Ground live answers in published knowledge, not draft notes.
Callaro knowledge bases are tenant-scoped collections of approved sources. Agents can link a published knowledge base instead of pasting large custom knowledge text into the prompt.Knowledge-base CRUD lives on
/api/v1/knowledge-bases and related source routes. Those families are enforced in the API key permission matrix (knowledge_bases:read / knowledge_bases:write) but are not yet fully generated in public OpenAPI. Use this guide plus the app UI until generated coverage lands.Recommended rollout
1
Create a docs-only knowledge base
Start with one domain (pricing, eligibility, or office hours). Avoid mixing unrelated policies in the same corpus.
2
Add sources and wait for processing
Upload files or website sources from Knowledge base. Confirm each source reaches a ready state before publish.
3
Publish, then link from the agent
In the agent wizard Prompt & Goals step, choose a linked published knowledge base instead of unbounded custom text.
4
Verify on a sandbox call
Ask a question that only the knowledge base can answer. Confirm the transcript stays on-policy and does not invent missing facts.
Scope and billing notes
- Website imports and file-extraction fallback can create knowledge-base usage events in tenant billing.
- Linking is typically plan-gated in the product UI. If the card is locked, publish the KB first and confirm the tenant plan includes retrieval.
- Keep sandbox and production knowledge bases isolated. Draft sandbox content must not serve production callers.
API key scopes
Failure modes
What to do next
- Review the product concept page
../concepts/knowledge-retrieval. - Review Help Center article Knowledge bases after Help Scout publish.
- Track generated-spec progress on
../api-reference/openapi-coverage-status.