Skip to main content
Short answers to what evaluators and developers ask most, each linking to the page that covers it in full. In one line: MITHUNAI answers questions from your own documentation, repositories and files, cites the passages behind every answer, and says it does not know when your content does not cover the question.
An AI knowledge and answer platform. You connect your documentation, repositories and files; MITHUNAI ingests and indexes them and answers questions about them with citations, through a website widget, an HTTP API, an MCP server and its own console.
It is built not to. Answers are generated from passages retrieved from your content and checked against them. When the evidence does not support an answer, the assistant says it does not know. See How answers work.
Because your content did not support an answer. That is the product working as intended. Each abstention points at a gap in your content; the unanswered questions report collects them.
No, deliberately. A general-knowledge answer about your product is a guess presented under your brand. Guidance cannot override this.
Every answer lists citations to the passages it used, with a title, link and excerpt. Citations come from the retrieved evidence, not from the model, so they point at real passages.
MITHUNAI does not train models on your content. To answer a question, relevant passages are sent to your deployment’s configured model provider under that provider’s terms.
No. Retrieval is scoped to the asking assistant’s knowledge within your organisation, and the organisation is derived from the verified credential on every request. See Security.
Websites, sitemaps, GitHub repositories, and uploaded PDF, Word, Markdown and text files. See Knowledge sources.
Re-sync sources when your content changes. MITHUNAI does not re-sync on a schedule yet, so trigger sync from your publishing pipeline or a scheduled job.
Any model in your deployment’s catalogue. Each assistant can use a different one. See Create and configure assistants.
Yes, with the widget: one snippet copied from the console, restricted to the origins you allow, for visitors who never sign in.
Yes. Create an API key and call the HTTP API with Authorization: Bearer arukz_sk_….
Yes, through the MCP server, which offers three read-only tools for listing, searching and asking.
Yes. Set your product name, logo, favicon, colours and links per organisation, and they apply to the console and the widget. See Branding.
The question fails: Send a message returns 502 provider_failure, and a streamed answer ends with answer.error, or with answer.interrupted if part of the answer was already written. Earlier turns in the conversation are unaffected. Retry with backoff; see Errors.
Requests are rate limited per minute. See Rate limits. Longer-term usage quotas are planned.
Not yet. Both are planned. See Product status.
Not today. MITHUNAI answers questions; it does not act in other systems. See Product status.
Last modified on September 26, 2026