Every MITHUNAI feature, with the endpoints behind it

MITHUNAI connects your documentation, repositories and files, answers questions from them with citations, abstains when they do not support an answer, and serves those answers through a console, an HTTP API, a website widget and an MCP server. Every feature below is available unless marked Beta, and each is reachable over the API at the paths shown, relative to /mithunai/api/v1. Anything not listed here is not part of the product; Product status lists what is planned.

Knowledge

Feature	Endpoints	Guide
Collections, the corpus an assistant answers from	`GET/POST /knowledge/collections`, `PATCH /knowledge/collections/{id}`	Knowledge overview
Website crawl and sitemap sources, same origin only	`POST /knowledge/sources`	Sources
GitHub repository sources, at a branch, tag or commit	`POST /knowledge/sources`	Sources
GitHub issues and pull requests as sources; discussions (Beta)	`POST /knowledge/sources`	Sources
OpenAPI schemas, one document per operation	`POST /knowledge/sources`	Sources
Custom answers: up to 25 question-and-answer pairs you write	`POST /knowledge/sources`	Sources
Public Zendesk help centres and public Discourse forums	`POST /knowledge/sources`	Sources
Saved connections: your organisation’s own GitHub, Atlassian, Notion or Zendesk token, stored encrypted	`GET/POST /connections`, `GET/DELETE /connections/{id}`, `POST /connections/{id}/rotate`	Saved connections
Private GitHub repositories, read with a saved connection (Beta)	`POST /knowledge/sources` with `connection_id`	Private GitHub
Confluence Cloud and Notion, read with a saved connection (Beta)	`POST /knowledge/sources` with `connection_id`	Confluence, Notion
Jira Cloud issues, Jira Service Management requests and Zendesk solved tickets, read with a saved connection; public replies only (Beta)	`POST /knowledge/sources` with `connection_id`	Jira, Jira Service Management, Zendesk tickets
Editing, renaming, pausing and resuming a source	`PATCH /knowledge/sources/{id}`	Sources
File uploads: PDF, Word (`.docx`), Markdown, reStructuredText, HTML, text and source code	`POST /knowledge/uploads`, then `POST /knowledge/sources`	File uploads
Background ingestion with progress, retries and cancellation	`POST /knowledge/sources/{id}/sync`, `GET /knowledge/jobs/{id}`, `POST /knowledge/jobs/{id}/cancel`	Ingestion
Unchanged documents skipped on re-sync	Reported as `documents_unchanged` on the job	Ingestion
Secret redaction before indexing, and fetching that cannot reach private networks	Applied to every source	Security

Re-syncing is manual or scripted on every deployment. A deployment can also re-sync sources on one deployment-wide interval, which is off unless its operator turns it on: see Scheduled re-sync. There is no push-triggered sync.

Answers

Feature	Endpoints	Guide
Hybrid retrieval: semantic search combined with exact keyword matching	Used by every answer	Retrieval pipeline
Grounded answers with citations to the passages they used	`POST /conversations/{id}/messages`	How answers work
Abstention, with a reason	`abstained` and `abstention_reason` on the answer	Stream a message
Streaming answers over server-sent events	`POST /conversations/{id}/messages:stream`	Streaming
Stored conversations: list, rename, archive, delete	`GET/POST /conversations`, `PATCH/DELETE /conversations/{id}`	Conversations
Several assistants, each with its own knowledge, model and guidance	`GET/POST /assistants`, `PATCH /assistants/{id}`	Configure an assistant
The deployment’s model catalogue	`GET /models`, `GET /models/providers`	Models and providers

Channels

Feature	Endpoints	Guide
Console for your team	The same API, with a console session	Console walkthrough
HTTP API with API keys, stored only as hashes	`GET/POST /api-keys`, `DELETE /api-keys/{id}`	HTTP API
Website widget for anonymous visitors, limited to origins you allow	`/widget-deployments`, `/widget/*`	Website widget
A check that the widget’s line is on a page of your website	`POST /widget-deployments/{id}/installation-check`	What the check reports
MCP server with three read-only tools (Beta)	`POST /mcp`	MCP server
A Slack bot that answers in the thread, with sources (Beta)	`/integrations/slack`, `POST /slack/events`	Slack

Administration

Feature	Endpoints	Guide
Organisations isolated from each other, roles within each	Every endpoint	Organisations and roles
List members, add one by invitation, change a member’s role, and remove a member	`GET/POST /members`, `PATCH/DELETE /members/{account_id}`	Members
Invite a colleague by email (Beta: needs your deployment to send email)	`GET/POST /invitations`, `POST /invitations/{id}/resend`, `DELETE /invitations/{id}`	Invitations
Reset a forgotten password from the sign-in screen (Beta: needs email)	Console sign-in screen	Password reset
A monthly answer allowance per organisation, and this month’s use against it	`GET /usage`	Usage and limits
Usage counts by model and channel, for one assistant or all	`GET /analytics/usage`	Dashboard and usage
Coverage gaps: declined questions and answers rated unhelpful	`GET /analytics/unanswered`	Coverage gaps
Grouping similar coverage gaps, by meaning or wording (Beta)	`GET /analytics/unanswered?group=true`	Coverage gaps
Proposed answers: a coverage gap drafted from your sources, reviewed and published (Beta)	`GET /analytics/doc-proposals`, `POST /analytics/doc-proposals/{draft,publish,dismiss}`	Proposed answers
Top questions: what people ask most, never who asked (Beta)	`GET /analytics/top-questions`	Top questions
Source analytics: which sources and documents the answers cite	`GET /analytics/sources`	Source analytics
Transfer ownership of the organisation to another member	`POST /members/{account_id}/make-owner`	Members
White-label branding for the console and the widget	`GET/PUT/DELETE /branding`, `GET /branding/settings`	Branding
Consented, read-only access for MITHUNAI support	`GET/PUT /support-access`	Support access
Liveness and readiness probes	`GET /health`, `GET /ready`	Health

Not part of MITHUNAI today

Webhooks, SDKs, a command-line tool, tools that let an assistant act in other systems, self-service sign-up, changing your password while signed in, SSO with your own identity provider and SCIM, spend caps, plans and billing, per-user analytics, and any knowledge source that needs a sign-in other than GitHub, Confluence, Notion, Jira, Jira Service Management and Zendesk tickets: Slack, Discord, S3, Google Drive, Salesforce and YouTube are not supported as sources. Where one of these has a page in these docs, the page says what to use instead.

The other surfaces

This catalogue covers the console, the API, the widget and MCP. Chat, Agents (in beta, access on request) and the Model Gateway are further surfaces of the same product: see Other surfaces.

Get started

Resources

Every MITHUNAI feature, with the endpoints behind it

Knowledge

Answers

Channels

Administration

Not part of MITHUNAI today

The other surfaces

​Knowledge

​Answers

​Channels

​Administration

​Not part of MITHUNAI today

​The other surfaces

Knowledge

Answers

Channels

Administration

Not part of MITHUNAI today

The other surfaces