Skip to content

What it knows

Give it your documents, not a prompt.

Upload files or point it at a URL for what the agent should know. Write short procedures as skills for what it should do. Both change without a redeploy.

How it works

What the capability actually does.

Formats people actually have

Plain text, Markdown, PDF, and Word. Text extraction happens on upload, so there is no conversion step.

A whole help centre in one action

Import from a public URL with the navigation and footers stripped out, or paste a list of links, or hand it a sitemap. Anything imported from a URL can be re-synced later when the source changes.

Searched, not recited

Documents are chunked and indexed so the agent retrieves the relevant passage during the conversation rather than carrying everything in its instructions. A short essential document can be pinned so it is always present.

Skills are procedures, not passages

A skill is a short, admin-written procedure with a description of when to use it. The agent matches on that trigger description rather than on the body, then loads the whole procedure at once, because half a refund policy is worse than none. Orchestrators keep their own library.

No redeploy

Uploading takes effect on the next conversation. Changing what an agent knows, or how it handles a situation, is not a release.

In the product

The screens this happens on.

The knowledge tab listing indexed documents with their sync status

What it knows, and what is pinned

Documents an agent can draw on, each showing whether indexing finished, is still running, or failed. Anything imported from a URL keeps its source and can be re-synced when the page behind it changes. A short, essential document can be pinned so it is present in every conversation instead of waiting to be retrieved.

  • Plain text, Markdown, PDF, and Word
  • Uploading takes effect on the next conversation, with no redeploy
The skills tab listing admin-written procedures, each with the description that decides when it is used

Procedures, matched on when to use them

A skill is a procedure you write, paired with a description of when it applies. The match runs against that description rather than the body, which is why the trigger wording matters more than the length of the instructions. Once matched, the whole procedure loads at once: half a refund policy is worse than none.

  • Orchestrators keep their own separate library
Boundaries

What it deliberately does not do.

Stated here rather than discovered in production. Every one of these is a real constraint, and knowing them before you buy is worth more than a longer feature list.
  • Legacy .doc files from Word 97 to 2003 are not supported. Re-save as .docx or export a PDF.
  • A URL import needs the page to be publicly reachable.
  • A skill is matched on its trigger description, so a vague description is the usual reason one does not fire when expected.
Elsewhere

The rest of the platform.

See what it costsCompare it