1. Get access
Request access, or accept an invitation from a colleague whose organisation already uses MITHUNAI. There is no instant, self-service sign-up: a person reviews each request, and accounts and organisations are created by whoever operates your MITHUNAI deployment. To start, book a demo or talk to your MITHUNAI contact; to see answers first, try the public playground, which needs no account. Your organisation is created with its first Owner, who then signs in to the console at app.mithunai.com. Sign in with the email address and password you were given. If you forget your password, choose Forgot password? on the sign-in screen; this needs your deployment to be able to send email, and until it can, the operator sets passwords. See Password reset. The same account also opens Chat. For Agents and the Model Gateway, see One sign-in.2. Add your team
An Owner or Administrator invites colleagues in Settings → Members under Invite by email, naming each one’s email address and role. Each person gets a link, valid once for seven days, and chooses their own password; nobody needs an account first. Roles can be changed and members removed from the same screen. See Invitations and Members.Invitations need your deployment to be able to send email, which is off until its operator sets up
a mail provider. Until then the invite form is turned off, and nobody new can be added: a member
is added only by invitation, including through
POST /members.
See Organisations and roles.
3. Connect and ingest knowledge
In Sources → Connect source, add a Sitemap, Website, File upload, OpenAPI schema, public Zendesk Help Center, public Discourse forum or GitHub repository, or write Custom answers. Confluence, Notion, Jira, Jira Service Management, Zendesk tickets and a private GitHub repository, all in beta, read with a token your organisation saves once as a connection. Ingestion starts on its own and runs in the background; credentials found in your content are redacted before indexing. Wait for the job to finish with statussucceeded, or partial if some documents failed, before asking questions.
- Sources and File uploads cover each source’s settings.
- Connectors lists what cannot be connected and what to do instead.
- Ingestion explains job statuses. Re-sync when your content changes; a deployment’s own scheduled re-sync is off unless its operator has turned it on.
4. Create an assistant
In Customizations → New assistant, give it a name, tick the collections it should answer from, and optionally choose a model and write guidance for its audience and tone. Guidance shapes how answers read; it cannot make the assistant answer beyond your content. See Configure an assistant, Models and providers and Guidance.5. Test it
Ask 20 to 50 real questions in the Playground before anyone else sees the assistant. Check three things: it answers what your content covers, it abstains on what it does not, and its citations open the right passage. Evaluate an assistant has a question checklist and a script.6. Launch on a channel
Website widget
Under Integrations → Website widget, enter your website’s address, paste the one line into
your site, and select Check my website.
HTTP API
Create an API key under API keys and call the API from your backend.
MCP server
Give each person or tool its own Member API key to connect Claude Code, Cursor or VS Code. Beta,
read-only.