Overview, usage history and cost analysis

Dashboard overview#

Overview presents balance, daily spend, daily tokens and requests, model share, total tokens and trends. k, m and b denote thousands, millions and billions; monetary values use the displayed USD unit.

Refresh to retrieve the latest overview. When loading fails, retry rather than interpreting missing data as a true zero balance or usage. Open announcements for full details and use the overview board for recent notices.

Reconcile per request#

• Filter by date, provider and supported fields, paying attention to the displayed time zone.
• Distinguish buffered and streaming requests and check status, model, group and input/output tokens.
• Keep request and task ids to connect client errors, agent logs and usage records.
• Cache and reasoning categories may differ from ordinary input/output; do not double-count overlapping fields.

Investigate unexpected usage#

Check whether loops, multiple clients or retries ran at the same time. Repeatedly sending long conversation history also increases input usage. Separate an initial call, retries and tool turns when explaining cost instead of looking only at the length of the final answer.