Skip to main content
MITHUNAI reports five things about your assistants: how much they are used and how often they answer, what people asked, what they ask most, which questions they could not answer, and which of your sources the answers cite. The first is the usage report on the Dashboard, beside your monthly answer allowance; the other four are the screens under Analyze in the console.

Conversations

What people asked and what the assistant answered, with the sources each answer cited.

Coverage gaps

Questions your assistants declined, and answers rated unhelpful.

Top questions

What people ask most, never who asked. Beta.

Source analytics

Which sources and documents the answers are built from.

​
The Dashboard

The Dashboard is the first screen after you sign in. Until an assistant can answer, it shows a setup guide instead of figures: connect your knowledge, wait for the first sync, point an assistant at it, ask a question, and put it on your website. Once an assistant can answer, it opens on the usage report’s headline figures, and below them shows:
  • Sources: how many you have and how many need attention. Selecting it opens Sources.
  • Coverage gaps: how many questions were declined or rated unhelpful in the last 30 days. Selecting it opens Coverage gaps. Owners and Administrators only.
  • Answers this month: how much of your monthly answer allowance is used. See Usage and limits. Owners, Administrators and Editors only.
  • The rest of the usage report, described below.
When your allowance is nearly used or used up, Answers this month moves to the top of the page.

​
Usage

The usage report covers the last 7, 30 or 90 days. Filter the report to one assistant to compare assistants. The report contains counts only, never question or answer text, and it has no latency or cost figures. With the API, use Get usage with days for a trailing window, or start and end for an exact range of up to 366 days. Owners, Administrators and Editors can read usage.

​
Reading the numbers

  • A high abstention rate usually means a content gap, not a product fault. Read Coverage gaps before changing anything else.
  • A sudden jump in abstentions after a change often means a source failed to sync or an assistant lost its knowledge. Check the ingestion jobs.
  • Failures point at the model provider or the deployment. If they persist, contact whoever operates your MITHUNAI deployment.

​
Source analytics

Source analytics shows which of your sources, and which documents in them, the answers were built from, with a CSV export. It has its own page: Source analytics.

​
Who can read what

The Conversations screen is in the sidebar for Owners and Administrators. Everyone else finds their own conversations in the Playground.

​
Not available

Cost reporting and a per-source trend over time are planned, with no committed date. A per-user view is not offered: no analytics screen shows what one person asked. What people ask most is on Top questions. See Product status.
Last modified on November 7, 2026