Knowledge bases

A knowledge base is a named set of sources: your website, your documents, pasted text, your own APIs and MCP servers. Amomic-AI reads each source, splits it into chunks, and makes them searchable. Any agent you connect to the knowledge base answers from those chunks.

This page is the how-to for the Knowledge page in the console. For how a question finds its chunks, and what to do when an agent says it doesn't know, read How retrieval works.

Who can do what

Members get a read-only page: the buttons for writing are not shown at all. A live API source is a tool the agent can call, so changing one is an admin decision.

Plan limits. Knowledge is on every plan. The number of knowledge bases you can create is capped by plan: 1 on Free, 3 on Starter, 10 on Growth, and no plan cap on Enterprise. Every workspace also has a hard ceiling of 50. Sources, chunks and crawled pages are not capped by plan. See Limits and plans.

The Knowledge page #

Open Knowledge in the sidebar. Each knowledge base is a card with its name, its description, how many sources it has and how many chunks they produced.

A Dynamic badge means the knowledge base contains something that changes without you touching it: an API or MCP source, or any source with a refresh schedule. A knowledge base built only from uploaded files and pasted text never shows it.

Chunks are the pieces your content is split into, about 1,600 characters each. The chunk count is a quick way to tell how much the agent can actually draw on. Live API sources and MCP servers add no chunks, because they are called at answer time instead of being stored.

To delete a knowledge base, hover its card and click the trash icon. See Delete a source or a knowledge base before you do.

Create a knowledge base #

If your plan's limit is reached, the console says Your plan includes 3 knowledge base(s). Upgrade to add more. (with your plan's number). At the workspace ceiling it says Knowledge base limit reached for this organization.

Split by topic, not by agent. One Warranty & service policy knowledge base can teach your chat agent, your phone agent and your booking agent at once. That is easier to maintain than three copies.

To rename a knowledge base or change its description, open it and click the pencil next to its name. The Edit knowledge base dialog has the same two fields.

Inside a knowledge base #

Click a card to open it. The header shows the description, the source count and the chunk count. Sources are listed on the left. Connected agents and the Retrieval tester are on the right.

Each source row shows:

• Its title. For a website this defaults to the address; for a file, the file name; for a live API source, the tool name.
• Its type and size. For example Website · 142 chunks. A live API source shows its tool name instead of a chunk count. An MCP server shows how many tools it offers.
• ↻ daily, ↻ weekly or ↻ monthly when it refreshes on a schedule.
• Key secured when it authenticates with headers you supplied. Hover it to see the header names.
• Action (amber) when it can change things in your systems, not only answer questions.
• Its status, on the right. See Source status.

Hover a row to reveal its actions: edit (pencil), Re-sync, and delete (trash). Edit and re-sync are hidden while the source is syncing.

Add a source #

Click Add source. The dialog has five tabs, one per source type.

When a source is added, the console says Source added — syncing now. and the row starts showing its progress.

Website #

How the crawler reads a site:

• It renders each page the way a browser does, so content that loads with JavaScript is read.
• It honours robots.txt.
• It reads the address you gave first. Then it reads the URLs in the site's sitemap.xml, then links it finds on the pages.
• It stays on the same host and its subdomains, ignoring www.. Starting at veloriahome.in also covers support.veloriahome.in. Starting at support.veloriahome.in stays on support.veloriahome.in.
• It skips cart, checkout and admin paths and non-page files, and treats URLs that differ only by query string (?utm_source=…) as the same page.
• It reads up to 60 pages per source. There is no page-limit, depth or include/exclude setting in the console.

Two addresses are refused before anything is created:

• That doesn't look like a valid website address.
• That address can't be reached from the crawler. The crawler only reaches the public internet. A staging site behind a VPN, an intranet or a private IP address can't be crawled.

While it runs, the row shows Crawling 34/57: pages read out of pages found so far, which grows as links are discovered.

Files #

Click Choose files and pick one or more files. Each uploads separately; when they are all sent, the console says Files uploading. and closes the dialog.

The limit is 15 MB per file. A file that's refused shows a toast with the file name and the reason, while the others carry on:

• Unsupported file type .pages — use PDF, DOCX, XLSX, CSV, TXT, MD or images.
• File is too large (max 15 MB).
• The file is empty.

Files are never re-read on a schedule. When a document changes, upload the new version and remove the old one. If both stay, the agent will sometimes quote last year's prices.

Text #

Text sources are where the facts that exist nowhere else belong: the escalation path, the exception you make for commercial customers, the number on the contact page that nobody answers any more. They are often the most valuable chunks you have. Keep each one to a single topic.

API #

Your own HTTPS endpoint, in one of two modes. Choose the mode first; the form changes with it.

Responses larger than 2 MB are refused. A live tool's answer is trimmed to a prompt-sized length before the agent reads it.

Tools and actions covers live tools and actions in depth: how the agent decides to call them, and the safety model for actions.

MCP #

Point at an MCP server and the tools it lists become abilities for your agent.

Click Connect server. When the row shows Connected, its detail line tells you how many tools were found. At most 20 tools from one server are used.

There is no test-connection button on the API or MCP tabs. Add the source and watch its status: Connected (or Synced ✓ when ingesting) means it worked; Failed shows the reason.

Source status #

The page checks for progress every few seconds while any source is busy, so you don't need to reload.

Re-syncs are last-good-serving. When a source is re-read, its old chunks keep answering until the new ones are stored, then they are swapped. A re-crawl never leaves an agent briefly knowing nothing. If the re-read fails, the old chunks stay in place.

A source showing Connected with no chunks is working correctly.

Keep it fresh #

Websites and ingested API sources can re-read themselves. Pick the interval in Keep it fresh when you add the source, or later by editing it.

There is no hourly option. If content changes more often than daily, use a live API source, which fetches at answer time.

• The next refresh is scheduled before a refresh starts, so a source that keeps failing retries at its next interval rather than in a loop.
• A source that is already syncing is skipped by the schedule.
• Re-sync on a row starts a refresh now. On a source that is already syncing the console says This source is already syncing.
• After a successful refresh every connected agent uses the new content straight away. On phone agents the call-time fact sheet is rebuilt too.

The refresh safety check. If a source that had at least 8 chunks comes back from a refresh with fewer than a quarter of them, the refresh is rejected and the old chunks keep serving. This protects you from a site redesign or a login wall silently emptying your agent's memory. The row shows Failed until the next successful re-read. If the content really did shrink that much, remove the source and add it again.

Edit a source #

Hover the row and click the pencil. You can change a source in place instead of deleting and re-adding it. The source keeps its identity, so a live tool stays the same tool to the agent.

Click Save changes. If your edit changed what the source knows (an address, the text, a method, a header), the console says Saved — re-syncing now. and reads it again. If you only changed metadata such as a title or a description, it says Source updated.

A source that is still syncing can't be edited. The dialog says This source is still syncing. Once it finishes you can edit it.

Credentials for authenticated sources #

API and MCP sources can send up to 10 HTTP headers: an API key, a bearer token, a client id.

• Header values go straight to encrypted secret storage when you save. They are never shown again, in the console or anywhere else. The console keeps only the header names and shows Key secured on the row.
• When you edit the source, saved headers show •••••••• unchanged. Leave the value empty to keep it. Type a new value only when you are replacing the credential.
• To fix a mistyped header name, rename the row and leave its value empty. The saved value moves to the new name: Renamed headers keep their saved value — you don't need to re-enter it.
• To remove a header, click the × on its row.
• The form checks each row: "X Key" isn't a valid header name., Enter a value for Authorization., Two headers have the same name., At most 10 headers.
• Authentication is header-based only. There is no OAuth flow and no client certificates.

If a stored credential goes missing, the source reports This source's credentials are missing; re-enter them on the source. Edit the source and type the value again.

Connect agents #

An agent answers only from knowledge bases connected to it. Creating a knowledge base doesn't teach any agent anything. There is no workspace-wide pool.

The Connected agents card lists every agent in the workspace, each marked Live or Draft. Live here means the agent's web chat widget is live. An agent that answers only on WhatsApp or the phone reads Draft, even while it is taking calls, so check the agent's Deployments tab for where it really runs. Click Connect or Disconnect. You can also attach a knowledge base from the agent's own Knowledge tab; see Agents.

The same knowledge base can teach several agents. That is the usual shape: one policy knowledge base connected to your chat agent, your phone agent and your booking agent.

Built-in knowledge. When you add sources while setting up a web chat widget, they go into a knowledge base named after the agent, such as Veloria Support knowledge. It works like any other knowledge base, but it can't be disconnected from its own agent: This is the bot's built-in knowledge — delete its sources instead of disconnecting.

Members see the same card with Connected or Not connected badges instead of buttons.

Delete a source or a knowledge base #

If you only want an agent to stop using a knowledge base, Disconnect it instead. The knowledge base and its sources stay intact.

Limits #

Troubleshooting #

Where to go next #