Read usage
Understand settled token counts, call totals, and daily spend.
Usage summarizes settled work for the recent 30-day period. It combines API and playground operations within the selected project. It does not estimate future spend from pending jobs or treat reserved credit as already consumed.
Summary metrics
Total spend is the sum of settled charges in the displayed period. Tokens combines recorded input and output inference tokens. Requests counts settled inference and internalization jobs. Internalizations counts settled learning operations, including rejected or failed ones, so it is not a count of active adapters.
These distinctions matter when estimating cost. Call counts do not determine charges: learning uses variable amounts of compute. Use actual settled charges for accounting and inspect request outcomes for success rates.
Daily view
The chart shows daily spend in USD using UTC dates. The table breaks out input tokens, output tokens, internalization calls, and cost. Output includes generated reasoning, even though raw reasoning is not returned to the caller.
Input and output totals include teacher, scoring, and validation calls as well as customer inference. Training tokens are reported separately on each job. Verified cache hits are a subset of input. The job’s compute and hosting amounts explain its settled charge.
Settlement timing
Daily usage is recorded when a job settles. A job admitted before midnight and completed after midnight appears in the later UTC day's settled usage. Similarly, work crossing a month boundary affects the month in which its charge settles.
The monthly spending limit is a calendar-month control in Settings. The Usage workspace is a recent-period view. Their totals need not match when the displayed recent period spans two calendar months.
Pending and zero usage
A running request may hold credit without appearing as settled spend. Read Billing for available and reserved balances, and Activity for the underlying job. A zero-token display on an unresolved job does not establish that the provider performed no work.
An empty chart is expected for a new project and for a hosted preview project that has not executed model work. The interface does not generate sample usage to fill the chart.
For exact per-operation accounting, read billing.charged_microusd and billing.settled on the job. Display rounding in a chart is not the ledger's precision. See Credits and pricing for calculations and Spending limits for admission controls.