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; Coverage gaps collects them.
Your website is probably still being read. The Ask AI button appears as soon as the line is on your page, and answers from your pages come once reading finishes. Watch the source under Sources; see Troubleshooting if it has finished and the widget still cannot answer.
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.
There is no self-service sign-up, and the console’s sign-up form does not create an account. A new organisation is created by whoever operates your MITHUNAI deployment: book a demo. To join an organisation that already uses MITHUNAI, ask its Owner or an Administrator to invite you by email; you choose your own password from the link.
Yes, where your deployment can send email: choose Forgot password? on the sign-in screen. The link works once, for 30 minutes. If email is not set up, the operator of your deployment sets a new password for you. See Password reset.
Chat serves one organisation and admits only its members. If you see “This account is not a member of the organisation this application belongs to”, your password is right and the membership is missing: ask an Owner or Administrator of that organisation to add you. Agents is a different case: it is in beta, with access on request. See One sign-in.
Three more surfaces of the same product: a chat workspace over your knowledge, agents that act (in beta, access on request), and one endpoint in front of model providers. Who can sign in to each differs: see Other surfaces.
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, uploaded PDF, Word, Markdown and text files, OpenAPI schemas, answers you write yourself, public Zendesk help centres, public Discourse forums, and GitHub repositories: their files, issues, pull requests and, in beta, discussions. In beta, a private GitHub repository, a Confluence Cloud site, a Notion workspace, Jira Cloud issues, a Jira Service Management desk’s requests and Zendesk solved tickets, each read with a token your organisation saves as a connection. No other source takes a credential, so a help centre or forum that needs signing in cannot be connected, and Google Drive and Slack are not supported. See Connectors.
In your organisation’s saved connections, encrypted at rest, and never shown again to anyone, including you and MITHUNAI support. Each token is sent only to the service it belongs to, and every use is recorded in your audit log. Whatever the token can read, your assistant can quote to anyone who can ask it, so give it read-only access to only what you want answered. See Saved connections.
Re-sync sources when your content changes: trigger sync from your publishing pipeline or a scheduled job. A deployment can also re-sync sources itself, on one interval for every source, but that is off unless its operator has turned it on. See Scheduled re-sync.
Any model in your deployment’s catalogue. Each assistant can use a different one. See Create and configure assistants.
Yes, with the widget. Under Integrations → Website widget, enter your website’s address, paste the one line the console gives you, and select Check my website. It works for visitors who never sign in, and only on the websites you allow.
Yes. Create an API key and call the HTTP API with Authorization: Bearer mithunai_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.
Two. Requests are rate limited per minute; see Rate limits. And each organisation has a monthly answer allowance: once it is used, new questions are refused with 429 quota_exceeded on every surface until the next calendar month. The Dashboard shows how much is used. It counts answers, not spend; there are no plans or billing yet. See Usage and limits.
What people ask most, yes: Analyze → Top questions lists it for the last 7, 30 or 90 days, with questions that mean the same thing counted together. Who asked, no: a question appears only once three different people have asked it, and no screen shows one person’s questions. See Top questions.
No. One MITHUNAI account signs in to the console and Chat; Agents and the Model Gateway offer the same sign-in beside a form of their own, which is in beta. Signing in with your own identity provider, and SCIM provisioning, are not available; both are planned, with no committed date. See One sign-in and Product status.
No. An assistant answers questions and changes nothing, and no guidance can make it act. Work that acts belongs to Agents, a separate surface that is in beta, with access on request. See Assistants and agents.
Last modified on November 7, 2026