Skip to main content
A Knowledge base groups one or more sources into something agents can search. All reading, chunking and embedding happen here, so one source can feed several KBs processed differently. Each KB has its own MCP / REST endpoints, so you can give it to each agent and revoke access independently.

KB list screen

Creating a knowledge base

The wizard has four steps: Select data → Processing pipeline → Name & access → Review & create.
1

Select data

Tick one or more sources; expand the folder tree to pick individual folders or files. The table shows file count and how many KBs use each source. Under System sources there is a ready-made Legal documents - An external index updated automatically every day. If data is missing, click Create new source →.
2

Processing pipeline

Choose a ready-made pipeline for each source - Automatic per file is recommended. The screen lists file counts by type and how each type is processed. The workspace default embedding model is used and locked once the KB is created.
3

Name & access

Enter the KB name and Description for the agent (agents read this line to decide when to call the KB; editable later in the Connect tab). Add KB managers - People who edit settings, review chunks and issue API keys.
4

Review & create

Check everything and create the KB. The system starts processing and indexing.

KB detail screen

The header summarizes document count, chunk count, owner and documents needing review, with the Retrieval test and Add data to KB buttons and the Data taken from block (which sources, all or part, Edit scope button).

Documents tab

A document table with columns Document, Source, Status (Processed, Processing error), Chunks. Filter All / Needs review / Disabled, choose Visible columns, Filter by metadata. Click a document to open the chunk viewer:

Needs review tab

A queue of work to handle, grouped by cause: Each item has a Fix in source button; use Bulk edit and Approve fixed items when handling many items.

Settings tab

Connect tab

Note: There are no document-level permissions yet - Anyone with a KB’s API key can query every document in it.