> ## 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.

# MITHUNAI RAG: answers from your knowledge, with citations

> MITHUNAI RAG connects your documentation and other sources, answers from them with citations, and deploys the answers through a widget, an API and MCP.

**MITHUNAI RAG** answers questions from your own content. You connect your documentation and other knowledge sources; it reads and indexes them, answers each question from the passages it retrieves, cites those passages, and says it does not know when your content does not cover the question. You then put those answers where people ask: a widget on your website, your own product over the HTTP API, and AI tools over MCP.

## At a glance

| | |
| - | - |
| **Who it is for** | Teams that publish documentation, a help centre or a product knowledge base and want customers and colleagues to get cited answers from it |
| **Where it lives** | In the console at [app.mithunai.com](https://app.mithunai.com/), and at its own address, `rag.mithunai.com`, in beta; see [Its own address](#its-own-address) |
| **Who can use it** | Every member of your organisation, with the same MITHUNAI account as everywhere else. What each person can change depends on their [role](https://docs.mithunai.com/concepts/organizations-and-roles.md) |
| **Status** | **Available.** A few parts are in beta; see [What is in beta](#what-is-in-beta) |

## What it does

> [card] [Connect knowledge](https://docs.mithunai.com/knowledge/overview.md)
>
> Websites, sitemaps, files, GitHub, Confluence, Notion, Jira, Zendesk, help centres, forums and
> answers you write yourself.

> [card] [Answer with citations](https://docs.mithunai.com/concepts/how-answers-work.md)
>
> Every answer is written from retrieved passages and cites them, or the assistant abstains.

> [card] [Configure assistants](https://docs.mithunai.com/assistants/configure.md)
>
> Choose an assistant's knowledge, model and guidance, and try it in the Playground.

> [card] [Deploy](https://docs.mithunai.com/channels/overview.md)
>
> The Ask AI website widget, the HTTP API with API keys, and an MCP server.

> [card] [Analyze](https://docs.mithunai.com/administration/analytics.md)
>
> Conversations, top questions, coverage gaps and which sources answers cite.

> [card] [API reference](https://docs.mithunai.com/api-reference/introduction.md)
>
> Every endpoint, with its parameters, responses and examples.

The rule that makes it RAG holds on every channel: an answer comes from your content, cites it, and is replaced by an abstention when the evidence is not strong enough. [How answers work](https://docs.mithunai.com/concepts/how-answers-work.md) explains each step.

## What is in beta

Most of MITHUNAI RAG is available. These parts are still new and still being worked on, and each carries a limit you should know about before you rely on it:

| Part | Its limit today |
| - | - |
| [MCP server](https://docs.mithunai.com/channels/mcp.md) | Three read-only tools: search, ask and list. No tool changes anything |
| [Confluence](https://docs.mithunai.com/knowledge/confluence.md) and [Notion](https://docs.mithunai.com/knowledge/notion.md) | Tested against scripted responses written from each service's documentation, not yet against a real site or workspace |
| [Private GitHub](https://docs.mithunai.com/knowledge/github-private.md) | Not yet run against a real private repository |
| [Jira](https://docs.mithunai.com/knowledge/jira.md), [Jira Service Management](https://docs.mithunai.com/knowledge/jira-service-management.md) and [Zendesk tickets](https://docs.mithunai.com/knowledge/zendesk-tickets.md) | Built against recorded responses, never yet run against a real account. Jira attachments, work logs, history and links are not read |
| [Coverage gaps](https://docs.mithunai.com/analyze/coverage-gaps.md) grouped by meaning | Falls back to grouping by wording when meaning cannot be compared, and says so |
| [Top questions](https://docs.mithunai.com/analyze/top-questions.md) | Lists a question only once three different people have asked it |
| [GitHub discussions](https://docs.mithunai.com/knowledge/connectors.md) | Needs a GitHub token or a saved connection |
| [Scheduled re-sync](https://docs.mithunai.com/knowledge/ingestion.md) | A deployment setting, off by default, with one interval for every source |
| [Invitations](https://docs.mithunai.com/administration/invitations.md) and [password reset](https://docs.mithunai.com/administration/password-reset.md) | Need your deployment to send email. A test message has arrived in a real inbox; these two messages have not yet been tried for real |

[Product status](https://docs.mithunai.com/resources/product-status.md) lists every capability and its status.

## Its own address

MITHUNAI RAG has its own address, `rag.mithunai.com`, in beta, signed in to with the same account. The console at [app.mithunai.com](https://app.mithunai.com/) stays where you work today. As the knowledge screens move:

* **Old addresses keep working.** A bookmark to a knowledge screen on `app.mithunai.com` opens the same screen at the new address.
* **Nothing you installed moves.** The widget script, the HTTP API base URL and the MCP address stay exactly as they are, so no website or integration needs changing.
* **Your account, organisation and members stay on the console.** They belong to the [platform](https://docs.mithunai.com/concepts/organizations-and-roles.md), which every MITHUNAI product shares.
* **You do not sign in twice.** See [Sign in once](https://docs.mithunai.com/platform/sign-in-once.md).

## Get started

[The quickstart](https://docs.mithunai.com/quickstart.md) goes from an empty organisation to a first cited answer in six steps. To put answers on your website first, see [Add Ask AI to your website](https://docs.mithunai.com/channels/widget.md).


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