Monthly reports
A month of your organization's usage in one document, as a printable page or CSV files.
A monthly report summarizes one calendar month of your organization's usage: what it cost, which teams, models and people used it, how reliable it was and, when your organization uses Insights, its coding sessions. You generate it under Organization › Settings › Reports, and you can have last month's report generated automatically on the 1st.
Monthly reports are off until a platform administrator switches them on for your organization. Only the organization's owners and admins can open the Reports tab.
Generate a report
- Open Settings under Organization in the sidebar, then the Reports tab.
- Choose a month. Months are calendar months in UTC. The current month is generated as month to date and is marked so on every page, because its figures still change.
- Select Generate report. The report is usually ready within seconds and appears in the list.
A report is frozen when it is generated: downloading it again later gives the same figures. To get current figures for a month that already has a report, choose the month and select Regenerate. The new report is added to the list and the earlier one stays.
Download it
Each finished report has three actions:
| Action | What you get |
|---|---|
| Open | The report in a new browser tab. Print it from there (Save as PDF) to keep a PDF. |
| HTML | The same page as a file you can share or archive. It needs no connection to Tokamak to open. |
| CSV | A zip of summary.csv, daily.csv, teams.csv, models.csv, members.csv and sessions.csv, with exact amounts you can add up in a spreadsheet. |
What the report contains
| Section | Contents |
|---|---|
| Summary | Usage cost, requests, tokens, active members, API keys, models and error rate, each compared with the previous calendar month. A short "Month in brief" is written from these figures. |
| Daily usage cost | Cost per day, with the previous month's daily average. |
| Usage by team | Cost, requests and members per team. A request's team comes from the API key that made it, so usage from keys that are not bound to a team is listed under No team. |
| Usage by model | The models used, with the same model reached through different providers shown once. |
| Top members | The ten members with the highest usage cost and the ten with the most tokens. Many tokens are cheap cache reads, which is why the two lists differ. |
| Reliability and routing | Error rate and kinds of error, response times, and how automatic routing was used. |
| Coding sessions | Shown when your organization uses Insights: sessions, commits and pull requests per coding tool. |
When the previous month did not record a figure (for example, months before API keys were recorded on each request), the report says Not recorded instead of showing a comparison.
Usage cost is the cost recorded on each request at catalog prices when it was served. It is not what your wallet was charged, and a report is not an invoice. For credit, purchases and receipts, see Credits and billing. Reports never contain prompt or response text.
Every month
At the bottom of the Reports tab:
- Generate last month's report on the 1st (on by default). Early on the 1st (UTC), once last month's figures have settled, its report is generated for you.
- Email owners and admins when it is ready (off by default). Each owner and admin receives a short email with a link to the Reports tab. The email contains no figures; they stay behind sign-in.
Guardrails
Screen what your organization sends to models. Find secrets, personal data and denylisted content in prompts, tool results and answers, and flag, mask, cloak or block it, with no client changes.
Credits and billing
Understand available credit, review purchases and distinguish payments from reported usage cost.