Knowledge Bases

Answers from what you know.

Your documents, links and files, for every agent.

Give your agents your handbook, product docs or policies, and their answers come from your own information rather than general knowledge.

What you can add

Sources, and the kinds of material teams add most.

  • Files
  • Web pages
  • Whole sites
  • Sitemaps
  • Notes and text
  • Google Drive
  • Handbooks
  • Policies
  • Product docs
  • FAQs
  • Course material
  • Research

How it works

From a folder of documents to answers.

  1. Add Knowledge

    Give the knowledge base a name, such as “Product Docs”.

  2. Choose its scope

    What it belongs to (the workspace, a module or an agent) and who can see it.

  3. Add sources

    Drop in files, paste links, type notes, or pick files from Google Drive.

  4. Index

    orchit reads everything, so agents can search it.

Keep it trustworthy

Knowledge that's current, and honest about its weight.

  • Trust levels

    From “Source of Truth” down to “Unverified”, so official material carries more weight.

  • Approve and re-index

    Review a knowledge base, approve or reject it, and re-index it after changes.

  • Fresh web pages

    Fetch web pages again whenever you need, or on a schedule.

Put it to work

A knowledge base helps the agents linked to it.

  • Connect it to agents

    Pick it in an agent's Knowledge settings, or from the knowledge base's Agents tab.

  • Ask in plain words

    “What's our refund policy for annual plans?”

  • Drive stays in sync

    orchit reads only the Drive files you pick, and their folders stay in sync.

Start building on orchit today

Describe your work, check the plan, and your workspace is ready to use in minutes.