Documentation menu
Build an agent
Knowledge base
A knowledge base has three parts. One rides in every prompt; the other two are searched on demand, so a large FAQ set or price list costs nothing on a call that never needs it.
The three parts
- Basic info
- Short facts that come up on nearly every call — who you are, hours, address. Included in the prompt directly.
- FAQs
- Question/answer pairs. Searched on demand, not prompt-stuffed.
- Other info
- Anything else — a policy doc, a price list. Also searched on demand.
An agent’s kbSettings (useBasicInfo, useFaqs, useOtherInfo) decide which of the three it draws on at all — turning one off removes it from the prompt or the search corpus entirely, not just from display.
How the search works
Attaching a knowledge base to an agent automatically gives it a search_knowledge_base tool — nothing to configure, the same way appointment booking’s commands appear once that’s turned on. FAQs and other info are broken into small, individually-searchable pieces (one per FAQ, one per paragraph); when the model calls the tool with what the caller asked about, it gets back the handful of pieces that actually match, not the entire document.
Importing from a website
Knowledge Base → Import from a website fetches a public page and drafts basic info, FAQs and other info from it using your OpenRouter key — review and edit the draft before saving it; nothing is written until you do.
Sharing a knowledge base
- One knowledge base can be attached to several agents at once — they all search the same content.
- Deleting a knowledge base unassigns it from every agent that had it, rather than leaving a dangling reference.