Usage & request history
Track costs by model and date, and inspect individual requests.
Track usage by model and date
The Usage page shows account-wide request counts, token usage, provider costs, and CyberRouter credits used. Filter by model and date, compare daily spending, and open individual request details.
Dates use UTC. The default is the last 30 days, and a query can cover up to 366 days. The dashboard stores usage metadata; it does not require opting into prompt or response collection.
Query usage and receipts
curl -G http://localhost:3002/v1/usage \
-H "Authorization: Bearer $CYBERROUTER_API_KEY" \
--data-urlencode "start=2026-09-01" \
--data-urlencode "end=2026-09-09" \
--data-urlencode "model=deepseek/deepseek-flash" \
--data-urlencode "limit=25" \
--data-urlencode "offset=0"Start and end dates are inclusive. The response contains summary, daily, models, requests, and pagination. Page size defaults to 25 and has a maximum of 100. Omit the model filter to include all models.
curl "http://localhost:3002/v1/generation?id=gen-example" \
-H "Authorization: Bearer $CYBERROUTER_API_KEY"Separate provider cost from credits used
| Field | Meaning |
|---|---|
| usage.cost | CyberRouter credits charged for the request, in USD. |
| usage.provider_cost | Provider API usage cost, paid separately through your provider account. |
| cyberrouter.service_fee_percent | Effective percentage snapshotted when this request started, including any privacy discount or account override. |
| cyberrouter.cost_is_estimate | Whether costs are estimated from reported tokens and configured prices, or usage is incomplete. |
| cyberrouter.billing_status | Settlement status, including requests that need reconciliation. |
When available, the provider’s reported dollar cost is the fee basis. Otherwise the gateway uses token usage and configured rates; the provider’s invoice may differ. Pending holds reduce available credits before final settlement. The Usage page distinguishes pending and incomplete billing from settled totals.