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

# AI answers from your own documentation

> MITHUNAI turns the documentation, repositories and files you already have into an assistant that answers questions about them, with citations you can check.

MITHUNAI turns the content you already have into an assistant that answers questions about it. Connect documentation sites, sitemaps, GitHub repositories and uploaded files. MITHUNAI ingests and indexes them, retrieves the passages relevant to each question, and answers with citations to those passages.

When your content does not support an answer, the assistant says so instead of guessing.

<Columns cols={3}>
  <Card title="Grounded" icon="shield-check">
    Each answer is checked against the passages retrieved from your content, not just prompted to
    stay on topic.
  </Card>

  <Card title="Cited" icon="quote">
    Every answer lists the sources behind it, with a title, link and excerpt your readers can
    verify.
  </Card>

  <Card title="Honest" icon="circle-help">
    When your content does not cover a question, the assistant declines to answer and flags the gap.
  </Card>
</Columns>

## Start here

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect a source, create an assistant and get your first cited answer.
  </Card>

  <Card title="Customer onboarding" icon="user-plus" href="/get-started/onboarding">
    Step-by-step enterprise journey from tenant setup to production launch.
  </Card>

  <Card title="Console walkthrough" icon="display" href="/get-started/console-walkthrough">
    Visual guide to the Ask Playground, Knowledge Manager, and Studio.
  </Card>

  <Card title="Features catalog" icon="list-check" href="/concepts/features-catalog">
    Complete index of all 20+ platform capabilities, endpoints, and specifications.
  </Card>

  <Card title="Supported connectors" icon="network" href="/knowledge/connectors">
    GitHub, GitLab, Notion, Confluence, S3, Google Drive, Zendesk, Slack.
  </Card>

  <Card title="API reference" icon="square-terminal" href="/api-reference/introduction">
    Every endpoint, with request and response examples.
  </Card>
</Columns>

## Platform & Architecture

<Columns cols={3}>
  <Card title="Inference Gateway" icon="zap" href="/concepts/gateway">
    Sub-45ms semantic cache, model routing and prompt fencing.
  </Card>

  <Card title="Retrieval Pipeline" icon="magnifying-glass-chart" href="/concepts/retrieval-pipeline">
    Hybrid BM25 + dense vector search, cross-encoder reranking, and verification.
  </Card>

  <Card title="Agent Studio" icon="workflow" href="/concepts/agent-studio">
    Multi-agent state graphs, tool authorization and human approval gates.
  </Card>

  <Card title="Autonomous Agents" icon="robot" href="/concepts/autonomous-agents">
    Goal-directed execution loops, tool sandboxing and durable memory.
  </Card>

  <Card title="Use Cases & Architecture" icon="diagram-project" href="/concepts/use-cases">
    Detailed workflows for docs AI, runbooks, support, and compliance.
  </Card>

  <Card title="System Architecture" icon="layer-group" href="/concepts/architecture">
    Six-layer dependency rules and Architectural Decision Records.
  </Card>
</Columns>

## Put answers where people ask

The same assistant, knowledge and grounding serve every channel. The channel changes how people ask, not the answer they get.

<Columns cols={3}>
  <Card title="Website widget" icon="message-square" href="/channels/widget">
    Embed a chat assistant on your documentation or support site for anonymous visitors.
  </Card>

  <Card title="HTTP API" icon="code" href="/channels/api">
    Build answers into your own product, portal or support tooling.
  </Card>

  <Card title="MCP server" icon="plug" href="/channels/mcp">
    Let Claude, IDE assistants and other MCP clients search and ask your knowledge.
  </Card>
</Columns>

## Built for content people act on

MITHUNAI is for teams whose users repeatedly ask questions that the documentation, API references, runbooks or code already answer, and where a wrong answer costs more than no answer. Typical uses:

* **Developer documentation**: answer integration questions on your docs site, with links to the exact section.
* **Customer support**: deflect repeat questions and surface the gaps your content does not yet cover.
* **Internal engineering knowledge**: give teams one place to ask about runbooks, architecture notes and repositories.
* **Compliance & security audits**: audit enterprise policies, SOC 2 controls, and vendor risk matrices with verified citations.

## Before you commit

<Columns cols={3}>
  <Card title="Security and isolation" icon="shield-check" href="/security">
    How your data is kept apart, who can reach it, and what is done with the content you ingest.
  </Card>

  <Card title="What is available today" icon="list-checks" href="/resources/product-status">
    Generally available, preview and planned, feature by feature, with nothing overstated.
  </Card>

  <Card title="Frequently asked questions" icon="circle-help" href="/resources/faq">
    Does it make things up, is your content used for training, can another customer see it.
  </Card>
</Columns>