Usage summary
Daily cost and activity for a project, broken down per model and summed across all models.
Overview
The usage summary is a project's cost and activity rolled up by UTC day, per model and across all models. It is the same data behind the project's Usage page in the Soniox Console.
Use it to:
- Report spend - total cost for a billing period, or per model.
- Chart trends - plot daily cost or request volume over weeks and months.
- Attribute cost - see which models account for most of the spend.
For a per-request record instead, see usage logs.
Summaries are available via the GET /v1/usage/summary API.
Choosing a window
start_time is inclusive and end_time is exclusive, both ISO 8601 UTC. A UTC day is included when the window covers
any part of it, so an end_time at exactly midnight leaves out its own day: 2026-04-01T00:00:00Z to
2026-04-03T00:00:00Z returns April 1 and April 2. A window may cover at most 366 UTC days.
What gets returned
The response has a total entry covering all models, and a models array with one entry per model that recorded usage.
The total entry is the one with a model of null, and a project with no usage gets an empty models array.
Every entry carries a days array of UTC dates, and the per-day arrays align to it by index. Every day in the window
appears, so days with no usage are zeros.
See GET /v1/usage/summary for the full schema and field types.
Only successfully started requests are counted. Requests rejected before they start - for example, due to an invalid API key, insufficient funds, or a validation error - are not included.
Usage logs
Per-request record of every transcription or speech generation processed by Soniox - model, audio duration, tokens, cost, and an optional client_reference_id.
Concurrency limits
Live counts of active real-time requests alongside the configured concurrency limits for the project and the organization that owns it, plus historical per-period concurrency.