The External knowledge screen lists the other knowledge bases this agent searches during a conversation, next to its own documents. Found in the agent sidebar under Knowledge → External. For how it works and when to use it, see External Knowledge.
Provider list
| |
|---|
| Add provider | Opens the type picker. Turned off when the agent already has 5 providers. |
| Provider | The provider's name, with its What information to look up here under it. Click a row to open it. |
| Source | The other agent's name (Agent Search API) or the endpoint's host (REST API). |
| Results | How many results are asked for in each search. |
| Status | Active; Off (switched off here); Search API off (the other agent's Search API is off or it became personal); Key revoked (the other agent revoked this provider's key); Agent deleted. |
| On | Switches the provider on or off at once. |
| Row menu | Edit, Test (opens the provider at its test), Make a new key (only when the key was revoked), Remove (asks first; an agent provider's key is revoked on the other agent). |
With no providers, an empty state explains the feature and offers Add provider.
Type picker
| Card | |
|---|
| Another agent's Search API | Search another agent you manage. Endpoint and key are filled in. 1 credit per search, charged to that agent's organization. |
| REST API | Any search service with the Search API contract. You enter the endpoint and key. |
| Knowledge gateway | Marked Coming soon; cannot be picked. |
Source (Another agent's Search API)
| |
|---|
| Agent | Agents you manage whose Search API is on, with their organization. Cannot be changed after the provider is added: remove it and add a new one. |
| Endpoint | The agent's Knowledge Search API address, with a copy button. Filled in for you. |
| API key | "Made automatically when you add the provider", then its last four characters. It is listed on the other agent's Search API page under Used by other agents. |
| Enforced codes notice | Shown when the other agent adds permission codes to every search anyway. |
Source (REST API)
| |
|---|
| Endpoint | Required. An https:// URL reachable on the internet. |
| API key | Required when adding. Stored encrypted and never shown again; when editing, leave it empty to keep the saved key. |
| Send the key as | X-Api-Key header or Authorization: Bearer. |
What the agent uses it for
| |
|---|
| Name | Required, up to 60 characters. Shown in citations. |
| What information to look up here | Required, 10 to 500 characters. The agent reads it to decide when to search this provider. |
| Use this provider in conversations | Switch it off to stop using the provider without removing it. |
Search
| |
|---|
| Permissions | Agent provider: codes picked from the other agent's permission list. REST provider: type a code and press Enter. Sent with every search. |
| Search results | 1 to 20, default 5. When this agent's reranker is on, results are reranked and cut to its number of search results. |
Test
| |
|---|
| Test question | The question to search for. |
| Run test | Runs one search with the form's values and lists the results (title, section, text, distance) in the provider's order, without reranking. A failure says why. An agent provider can be tested once it is added; a REST provider also before. |
The form asks before closing with unsaved changes. After you add a provider, it stays open on the new provider so you can test it.
- Channels → Search API → Used by other agents on the other agent: the keys made for providers, with Revoke. See Search API screen.
- Knowledge → Retrieval: the reranker that also applies to provider results.