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

# Three ways to reach your assistant

> One assistant, one body of knowledge and one grounding rule, reached three ways: an embeddable website widget, the HTTP API, and an MCP server for AI clients.

One assistant reaches people through four channels: a **website widget** for anonymous visitors on your own pages, an **HTTP API** for your own product or bot, an **MCP server** for Claude, IDE assistants and agent frameworks, and the **console** for your own team. Every channel reaches the same assistant, the same knowledge and the same grounding, so an answer is the same whichever channel it arrives through, and an abstention on one is an abstention on all. What differs is the credential and who is asking.

| Channel                            | For                                              | Credential                        | Who is asking                                |
| ---------------------------------- | ------------------------------------------------ | --------------------------------- | -------------------------------------------- |
| [Website widget](/channels/widget) | Your documentation, help centre or product pages | A public widget key, `arukz_wk_…` | Anonymous visitors                           |
| [HTTP API](/channels/api)          | Your own product, portal, bot or support tooling | An API key, `arukz_sk_…`          | Your backend, on behalf of your users        |
| [MCP server](/channels/mcp)        | Claude, IDE assistants and agent frameworks      | An API key, `arukz_sk_…`          | An AI client choosing when to look things up |
| Console                            | Your own team                                    | A console session                 | Signed-in members of your organisation       |

## Choosing a channel

<AccordionGroup>
  <Accordion title="I want a chat assistant on my website">
    Use the [widget](/channels/widget). It is one script tag, works for visitors who never sign in,
    and is bound to the origins you list.
  </Accordion>

  <Accordion title="I want answers inside my own product or bot">
    Use the [HTTP API](/channels/api) from your backend. Your server holds the API key and relays
    answers and citations to your interface. Stream them for a responsive experience.
  </Accordion>

  <Accordion title="I want my team's AI tools to use our documentation">
    Use the [MCP server](/channels/mcp). Claude, IDE assistants and other MCP clients can search
    your knowledge and ask your assistant, with citations.
  </Accordion>
</AccordionGroup>

## Usage by channel

The [usage report](/administration/analytics) breaks questions down by channel: `user` for the console, `service` for API keys (including MCP clients) and `widget` for embeds.