Knowledge base
Give an agent documents, web pages and text to answer from — shared across agents or kept local to one.
A knowledge base is the material an agent answers from: opening hours, price lists, policies, product documentation. The model retrieves the relevant passages during the conversation rather than carrying everything in its instructions.
What you can add
| Type | Use it for |
|---|---|
| Text | Short facts written directly in the dashboard |
| Existing documents, brochures, terms | |
| DOCX | Word documents |
| Web page | A single URL, fetched and indexed |
| Website | A site's structure, followed page by page |
Where an item lives
Every item has a scope:
- Reusable — kept in the workspace library and attached wherever it is needed. One source of truth for material several agents share.
- Flow — belongs to one flow.
- Agent — belongs to one agent.
Tip
Shared facts belong in reusable items. When the price list changes, you update it once instead of in every agent that quotes it.
Managing it from the API
An agent's knowledge base can be read and edited over the API — list, create, update and delete items — which is how most teams keep it in sync with a CMS or product database. See Knowledge base in the API reference.
Knowledge base or data store?
Use the knowledge base for prose the agent reads. Use a data store for records the agent looks up — a customer by phone number, a booking by reference — where an exact match matters more than a relevant passage.