Made for the way you work
Usage beside the work
Know what the work is using while it is happening. Keep the numbers close to the decisions that caused them.
In practice
A useful place to start
Compare the cost of a quick edit with a longer review. Expand the usage details to see which models and supporting work contributed.
Cost with context
Turn and session usage make spend easier to relate to actual work. Model attribution helps explain tasks that involve different providers, child agents, or side requests.
See more than a total
Token and cache information can show why two requests cost different amounts. Route information helps distinguish subscription-backed work from a direct API request.
Use the evidence
Change a model, thinking choice, or workflow based on observed usage. Reports can take the same kind of evidence across longer periods and more users.
Get started
Open the usage details in a chat and compare the model route with the work performed. Configure usage logs if you want longer-term reports.
Good to know
Cost is an estimate from available provider usage and catalog prices, not a guaranteed invoice. Unknown or unpriced usage is not free. Subscription quota is distinct from per-token API billing.