Knowledge Retrieval lets an agent or gateway search your
knowledge bases when it decides it needs to.
knowledge_search arguments
Per-binding configuration
One setting: knowledge_base_ids — which knowledge bases this binding may
search.
An empty list means no access. Binding Knowledge Retrieval without selecting
knowledge bases gives the agent three tools that find nothing. Select them in the
capability’s configuration when you bind it.
This is what lets you expose one knowledge base on a public gateway and a
different one to an internal agent, from the same account.
On-demand search versus automatic context
There are two ways to get knowledge into an agent, and they are not the same
mechanism:
- Attach knowledge bases to the agent directly. The platform retrieves
relevant material and puts it in the agent’s context. The agent does not choose
to search; the context is simply there.
- Bind this capability. The agent gets three tools and decides when to call
them.
Attach directly for an agent whose whole job is one corpus. Bind the capability
for a general agent that occasionally needs to look something up. Both together
is fine.
Cost
Metered per retrieval, plus knowledge-base storage and indexing. See
noorle.com/pricing.
Autonomy
Read tier, every tool — allowed at every autonomy level.
Next