Usage history
Open Usage from the Billing group to inspect reported consumption. Values follow the selected billing period and available usage snapshots.
Spend this period
- Read Spend this period for the period's credits and category breakdown.
- Choose This period or Last period. These are billing periods, not a monthly/daily toggle.
- Open a category to inspect the meters that contribute to its spending.
- Use the history charts for credits over time and stored bytes over time. Storage includes file and database bytes; a stored-byte snapshot is distinct from a cumulative byte-day charge.
Meters and charges
| Meter | What it measures |
|---|---|
Compute (compute_ms) | Server processing milliseconds |
Input/output tokens (tokens_in, tokens_out) | Model-weighted tokens, including applicable cache adjustments; platform BYOK exclusions apply |
Transcription (stt_ms) | Audio duration normalized by a per-model weight |
Synthesis (tts_ms) | Text-based duration estimate normalized by a per-model weight |
Transcoding (transcoding_ms) | Media processing milliseconds |
File/database storage (storage_byte_day, database_byte_day) | Stored bytes over time, billed by byte-day |
| Hosted channel uptime | Connected minutes for supported hosted channel types |
Only an actual eligible platform synthesis cache hit avoids a new synthesis charge. The cache is bounded and process-local; provider/model/voice/speed/instructions/format/text all affect the key. Repeating text within ten minutes does not guarantee a hit, and BYO synthesis bypasses this cache.
Understand changes in spending
Compare billing periods, then drill into the category that changed. Review agent prompts for token usage, active hosted connections for uptime, and retained files/records for storage charges. The wallet's available credit is a conservative estimate; the Usage page is not a promise of complete instantaneous settlement.
You can set budget limits and warnings through Budget. See Usage rates, Normalized tokens and Wallet & top-ups.