> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge base

> Create and organize knowledge documents, inspect their stored content, and review agent attachments and dependencies.

The knowledge base holds URL, text, and file documents in your workspace. Prepare accurate source material, inspect what was stored, and review the agents that reference it before changing or deleting a document.

<Frame caption="Recording pending: Add and review knowledge documents. Follow the written guide below.">
  <img src="https://mintcdn.com/threetonelabs-c2efc9c8/RV32i5440UZIaFHA/images/tutorials/recording-pending.webp?fit=max&auto=format&n=RV32i5440UZIaFHA&q=85&s=55f66d2eef49d8c92c9ac46f84bace35" alt="Recording pending for Add and review knowledge documents. No playable video is available yet." width="1600" height="900" className="w-full h-auto aspect-video" loading="lazy" noZoom data-path="images/tutorials/recording-pending.webp" />
</Frame>

## Choose a source

You need access to the workspace, permission to manage knowledge documents, and an existing target agent if you intend to attach the source. This procedure uses the API operations linked below; the dashboard can also be used to inspect workspace resources.

| Source | Use it for | API reference |
| - | - | - |
| Text | A small, reviewed passage you want to maintain directly. | [Create from text](/api-reference/agents-platform/create-knowledge-base-document-from-text) |
| File | A document you own and can replace when its content changes. | [Create from file](/api-reference/agents-platform/create-knowledge-base-document-from-file) |
| URL | A source page whose content you can inspect and keep current. | [Create from URL](/api-reference/agents-platform/create-knowledge-base-document-from-url) |
| Folder | An organizational container for related documents. | [Create a folder](/api-reference/conversational-ai/create-knowledge-base-folder) |

Keep credentials, private customer records, and information outside the agent's approved scope out of general-purpose knowledge documents. Give each source a clear name and an owner responsible for keeping it accurate.

## Add and inspect

<Steps>
  <Step title="Prepare reviewed content">
    Remove outdated instructions, repeated navigation, and irrelevant sections. Use descriptive headings and explicit facts that a reader can understand without the surrounding website layout.
  </Step>

  <Step title="Create the document">
    Add the source through the dashboard or the corresponding API operation. Keep the returned document identifier and organize related sources in folders.
  </Step>

  <Step title="Read metadata and content back">
    Inspect [document metadata](/api-reference/agents-platform/get-knowledge-base-document) and [document content](/api-reference/agents-platform/get-knowledge-base-document-content). Check that the stored representation contains the intended information.

    A successful create response alone does not prove that parsing, indexing, or retrieval has completed. Inspect the relevant status and content before attaching the source.
  </Step>

  <Step title="Review the agent attachment">
    Select the intended document in the agent configuration. Knowledge locators use `type`, `name`, `id`, and `usage_mode`; the usage mode is `auto` or `prompt`.

    Review the attachment with the agent's instructions and save a complete server draft on the intended branch. Check the stored references. Voice and custom-model publication are unavailable; only an eligible managed text-only configuration can use the current publication workflow.

    Attach knowledge to an existing agent after creation. The current create-agent path rejects a nonempty knowledge attachment list in the initial request.
  </Step>
</Steps>

<Frame caption="Screenshot pending: A synthetic knowledge document with its stored content and processing status.">
  <img src="https://mintcdn.com/threetonelabs-c2efc9c8/-FnvNeuT_PFanG1t/images/placeholders/screenshot-pending.svg?fit=max&auto=format&n=-FnvNeuT_PFanG1t&q=85&s=b29809bcbd6979cc43ace35853669b46" alt="Screenshot pending for A synthetic knowledge document with its stored content and processing status. This illustration is not a product screenshot." width="1600" height="1000" className="w-full h-auto" loading="lazy" noZoom data-path="images/placeholders/screenshot-pending.svg" />
</Frame>

## Storage and retrieval

Stored source content, processed document chunks, and retrieval during a live conversation are different stages. The API reference includes index and retrieval operations, but this guide does not claim that every ingestion or runtime retrieval path has been validated end to end.

<Note>
  Document creation or a saved attachment does not establish that a live agent answered from that source. Check [current availability](/agents-platform/overview#current-availability) and verify the ingestion and execution paths before relying on retrieval in an integration.
</Note>

## Update or remove a source

Check [agents using the document](/api-reference/agents-platform/list-agents-using-knowledge-base-document) before replacing or deleting it. The response is paginated: follow `next_cursor` while `has_more` is true, rather than relying only on the first page.

This dependency list covers active agent references and includes related nonarchived branches. It is not a complete inventory of references in historical versions. Review relevant branches and versions separately, since a change can affect more than the configuration currently open in the editor.

Use [Replace file](/api-reference/agents-platform/replace-knowledge-base-file) for a file source, [Move an item](/api-reference/conversational-ai/move-knowledge-base-item) to reorganize it, or [Delete document or folder](/api-reference/agents-platform/delete-knowledge-base-document-or-folder) when it is no longer needed. Read the affected content and references back after the operation. Do not assume URL documents automatically synchronize with later website changes.

## Troubleshooting

If content is empty or incomplete, inspect the source and stored representation before attaching it. If a document is unavailable to an agent, check its workspace, identifier, and resource access. If a delete or replacement affects existing agents, review dependencies and the intended configuration versions first.

Continue with [agent configuration](/agents-platform/configure/agent-behavior/overview) and [versions and drafts](/agents-platform/deploy/versioning).

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a created document prove retrieval is ready?" id="faq-knowledge-created">No. Inspect stored content and processing status. A saved attachment is separate from ingestion completion and retrieval during a live conversation.</Accordion>
  <Accordion title="Can I attach knowledge in the initial agent creation request?" id="faq-knowledge-initial-agent">The documented create-agent path rejects a nonempty knowledge list. Attach the source to an existing agent and read its saved configuration back.</Accordion>
  <Accordion title="Is the first dependency page enough before deletion?" id="faq-knowledge-dependency-pages">No. Follow the returned cursor while has\_more is true. Review relevant branches and historical versions separately because the dependency list is not a complete historical inventory.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.