Usage analytics
Track API usage, monitor credit consumption, and analyze account activity.
Overview
The Usage tab on the dashboard rolls up everything you have spent in the current billing cycle and lets you slice the data by feature, time window, and API key. It is the single source of truth for "where are my credits going?". The same data is available programmatically via the Usage API if you want to ship it to your own dashboards or trigger alerts.
Cycle summary
The top of the page shows the rollup for your current billing cycle: total credits consumed, what is still in your plan allocation, and the renewal date. Credits are prepaid, so none of this turns into a bill when the cycle closes — it is a record of what you already paid for and how much of it you have spent.
Breakdown by service
Credits are broken down across the three resource types the API tracks: voice_call (live phone or WebRTC conversations), tts (standalone text-to-speech requests), and transcription (audio-to-text). Each shows total credits spent in the cycle, request count, and a per-feature spark line so you can see which features are growing.
Daily and monthly view
Switch to Daily to see a per-day credit-spend bar chart for the last 30 days, or Monthly for a 12-month rollup. Useful when investigating spikes ("why did my Tuesday bill 3x my Monday?") or when planning capacity for the next month.
Per-API-key breakdown
If you have multiple API keys (per service, per customer, per environment), each request records which key authenticated it. The dashboard groups your usage by key so you can see which one is driving spend. Useful for billing customers through, debugging a runaway integration, or splitting bookkeeping across environments.
Programmatic access
Everything on the dashboard is exposed on the Usage API. The two most useful endpoints: GET /api/v1/usage/summary returns the cycle rollup, GET /api/v1/usage/daily?days=30 returns per-day credit spend. Both require the usage:read scope.