Token Usage
Review tokens per completed task and token composition.
Open Analytics → Token Usage to see whether finished work is getting cheaper and where tokens went. Choose Weekly or Monthly near the top of the page.
Read the metrics
Section titled “Read the metrics”| Metric | Meaning |
|---|---|
| Cost per completion | The estimated cost of the period divided by the number of completions |
| Cost of failed and abandoned work | The cost of subtasks that failed or were abandoned, and its share of the total |
| Token composition | The share of input, output, cache read, and cache write tokens |
| Model mix | The share of the estimated cost by model |
Cost per completion by period shows the last five periods. The cost is an estimate at catalog list prices. When some requests have no price, only a partial sum is shown, together with how many subtasks and requests it covers. A lower cost per completion does not by itself mean the same quality of result, because model and task mix change it.
Investigate usage
Section titled “Investigate usage”- Select a period and inspect the trend.
- Compare the completed count and the counted code groups; small samples can move the figure substantially.
- Review the token composition and the model mix, and open related work in Sessions.
- Use Telemetry for broader usage and Rightsizing for cost references.
Small or unevaluated work can be absent from scored totals. See Scores and work status.
Estimated costs are not billed amounts. An unavailable or partial cost should not be treated as zero or a complete total; see Periods and data states.