Usage

The usage resource exposes a 30-day rolling event total + COGS estimate for the caller's tenant. Useful for surfacing your own usage in an internal admin dashboard, sanity-checking the dashboard's counts against your own ingest counters, or feeding an internal chargeback / showback report.

Singleton, no :id

A bearer token can only ever read its own tenant's usage — same shape as tenant. The path is GET /v1/usage exactly; there is no list-form, no per-service breakdown in v1, and no write path (usage is a derived snapshot written by a daily aggregation cron).

Window semantics

The window is the last 30 days rolling, aggregated from per-day snapshots. events_total counts every event that reached the ingest endpoint, including events that were dropped by storm protection (storm-dropped events count toward usage by design — they still occupied ingest capacity). cogs_estimate_usd is an internal estimate of OpenAI + Anthropic spend on those events, useful as a ballpark, not as an invoice.

Brand-new tenants

If your tenant has no aggregation snapshots yet (the daily cron hasn't run since you signed up), the response returns zeros and a synthetic window of [now - 30d, now] rather than 404. This makes the response shape stable for tooling that polls the endpoint from day one.

Notes

  • Pricing is flat per service ($49/mo). Usage is reported here for visibility — there are no overage charges, regardless of events_total.
  • See our fair-use policy for what happens at sustained abnormally high volumes.

Endpoints