Skip to main content
A knowledge base is the workspace where everything comes together. It holds the documents your assistant answers from, the database connections it can query, the prompts that shape its voice, the agents built on top of it, and the chats that run against it. Most of your day-to-day configuration happens here. Every knowledge base belongs to exactly one tenant, and retrieval stays within its private corpus. Agent sharing passes another agent’s final answer to the caller without exposing or merging the other knowledge base’s documents.

​
What a knowledge base contains

Documents

The searchable corpus. Upload files, ingest a URL, or crawl a website, and the assistant answers from grounded, cited passages.

Prompts

Shape who the assistant is and how it answers with a persona, instructions, and optional full custom prompts.

Memory modes

Decide whether and how this knowledge base remembers durable facts across conversations.

Agent sharing

Let agents in other knowledge bases delegate to this one — while keeping your documents private.

​
Anatomy

A human-friendly name and description that identify the knowledge base in the dashboard and help your team tell them apart. The description is a good place to note what the corpus covers and who it is for.
A knowledge base can be active, inactive, pending, or suspended. An active knowledge base is ready to answer questions; the other states let you stage or pause a knowledge base without deleting its content.
The corpus the assistant retrieves from. Documents are processed in the background and become searchable once they reach the processed state. See Documents & ingestion.
Optional read connections that let the assistant query your live data and chart the results, alongside answers grounded in your documents.
The persona, instructions, and optional custom prompts that define the assistant’s voice and rules. See Prompts.
Saved, deployable configurations that run on this knowledge base. See Agents.

​
Quotas

Each tenant comes with quotas that keep usage predictable:
​
max knowledge bases
number
The most knowledge bases the tenant can hold.
​
max documents
number
The most documents the tenant can store across all of its knowledge bases.
​
max storage
number
The total storage the tenant’s documents can occupy.
When a new knowledge base or document would push a tenant past one of its quotas, the request is refused with a clear message telling you which limit was reached. Remove content you no longer need, or raise the tenant’s quota, and try again.

​
Create a knowledge base

1

Name it

Give the knowledge base a clear name and a short description of what it covers.
2

Add content

Upload documents, ingest a URL or website, and optionally add a database connection. See Documents & ingestion.
3

Shape the voice

Set a persona and instructions so the assistant answers in the tone and within the rules you want. See Prompts.
4

Start chatting or build an agent

Ask questions directly, or save the configuration as an agent you can deploy, schedule, or call through the API.

​
Next steps

Add documents

Upload files, ingest a URL, or crawl a website.

Shape the assistant

Set a persona, instructions, and custom prompts.