Knowledge base
The knowledge base gathers what your agents need to know: procedures, FAQs, terms, product sheets, reference documents. It belongs to your organization; an agent consults it when it needs to, through a tool, instead of carrying everything in its mission.
What it contains
Three types of entries:
| Type | Content |
|---|---|
| Entry | A Markdown text, written directly in the admin |
| Document | An uploaded file, whose text is extracted automatically for agents |
| Folder | A binder to organize entries and documents |
Accepted document formats: PDF, Word (.doc, .docx), Excel (.xls, .xlsx), PowerPoint (.ppt, .pptx), text, Markdown, HTML, CSV and images — up to 50 MB per file.
Extraction reads the text of office formats and PDFs. For an image or a scanned PDF (with almost no text), it goes through your organization's multimodal (vision) model. A failed extraction can be restarted from the admin.
Every write to the base is logged. Modifying it requires access to the Knowledge & indexing section; reading is open to the organization's members.
What your agents do with it
Two tools, to attach to an agent:
knowledge.search— keyword search, weighted (tags, then name, description, content). Returns the most relevant entry.knowledge.semantic_search— semantic search (by meaning, not by exact words). Returns excerpts with their source and score.
Results are presented to the agent as source material: it replies in the user's language and must not assert beyond what the source says.
Semantic search
For semantic search, entries and the text extracted from documents are split and indexed in a vector database (Qdrant). Embeddings are computed by the bge-m3 model, served by Ollama inside our infrastructure: the text of your base is not sent to a third-party embeddings provider.
Synchronization is automatic: a created or modified entry is re-indexed, a deleted entry is removed from the index, and a failed indexing is retried. Semantic search depends on it being enabled on the instance; otherwise, the tool directs the agent to knowledge.search.
Per-model scope
By default, a model searches the whole base of its organization. You can restrict what it sees, from the model's Knowledge base tab:
- checking a folder gives access to all its content, including what will be added later;
- checking an entry or a document gives access to that item only.
The same scope applies to both search tools. It is a relevance tool (an HR assistant has no need to read the sales FAQ); security isolation, for its part, is that of the organization: one organization's base is never readable by another.
Sharing a document by link
An entry or a document can be published by link (/shared/…), for a partner or a customer who has no betool account. Folders cannot be shared.
- Optional password — also required to download the file.
- Optional expiration, from 1 day to 5 years; without expiration, the link lives until it is revoked.
- Revocation at any time; republishing creates a new link and revokes the old one; deleting the entry revokes its link. A revoked, expired or unknown link returns the same not-found page.
- Rendering: a PDF or an image is displayed in the page; a Markdown document is rendered formatted; an HTML page is displayed in an isolated frame (no scripts or remote resources). Other formats are downloaded, with the extracted text displayed when it exists.
- Shared pages are not indexable by search engines, and the number of views is tracked.
Updating without changing the link
Replacing the file of a document keeps its identifier, and therefore the link already distributed: it immediately serves the new version. The text read by agents is re-extracted from the new file, so what your agents read and what your partner sees cannot diverge.
Updating by proposal
An agent (or an application connected via MCP) can propose changes to the base, subject to human validation:
knowledge_update— create or update a text entry (full replacement, replacement of a section, or appending at the end).knowledge_document_replace— replace a document's file, in place, public link kept.
Nothing is applied without an explicit Accept.