Statistics AI usage tab
Open Dashboard → Statistics → AI usage to inspect recorded AI activity in the selected range. Translation, review, chat, and other assisted tasks can involve requests. A request is not the same as a translated segment or a completed project.
Read the summary cards
| Card | Meaning |
|---|---|
| Usage | Recorded usage amount compared with the allowance calculated for the selected range |
| Tokens | Sum of recorded input and output tokens |
| Requests | Number of recorded usage requests in the range |
Tokens measure the input and output processed by a request. Input includes supplied instructions and context as well as the text being worked on; output includes the recorded response. The total is not a source-word count or a count of final accepted translations.
Requests are not clicks or accepted proposals
One action can make several requests, for example when it processes segments in batches. Requests counts those requests, rather than clicks on Translate or accepted proposals.
How Usage percentage is calculated
Usage uses recorded usage amounts and the relevant monthly allowance. It is not calculated by dividing the Tokens card by a token limit.
For a range touching several calendar months, the allowance is the monthly amount multiplied by the number of calendar months included. A partial month counts as a month in this calculation. For example, a range covering parts of two months uses two monthly allowance amounts rather than a day-by-day allowance.
The displayed percentage is capped at 100%. If the necessary allowance or recorded cost information is unavailable, Usage can show N/A. Recorded token activity with no charged amount can also differ from a positive allowance percentage.
Use the account's current allowance controls for current availability. A historical chart or selected-range percentage is not a promise that a particular action can run now.
Request size
The horizontal axis shows the selected days, weeks, or months. The vertical value is:
Average tokens per request = total recorded tokens / recorded request countA larger request can contain more text, instructions, context, or output. The chart does not rate the quality, speed, or success of the result. A smaller request is not automatically a better request.
Compare this chart with the Requests total and Usage overview. A large total can result from many small requests, fewer large requests, or both.
Usage overview
This chart shows the total recorded tokens in each time group. Choose Daily, Weekly, or Monthly where offered, and Line or Bar for the available presentation. Hover to read a group's value.
The date range still controls which usage records are included. Changing grouping does not change the selected period or remove requests from the records.
Why usage data is missing
If usage records cannot be loaded, the tab displays an unavailable message. Do not treat that state as zero usage. Individual charts can also be hidden when the range has no qualifying request or token values.
Check the selected dates and account/workspace before interpreting an empty view. The tab describes recorded usage available to this account; it is not a universal audit of every service or external application you may use.
See AI actions for choosing an operation, Chat for controlling supplied context, and Settings and account for current account choices.