Authentication
GET /api/v1/tenants/me/usage and GET /api/v1/tenant/usage require a dashboard session (cookie-based). They are used by the dashboard’s MAD meter and upgrade banner.
GET /api/v1/org/usage returns the same canonical shape and additionally accepts an API key with the org:read scope, so scripts and the CLI can read usage. See Console usage.
Responses are cached in Redis for 5 minutes per organization, so values may lag real-time attestation activity slightly.
Billing period
- Paid plans (Stripe): the period follows your Stripe billing cycle; the period start is one month before the current period end.
- Free plan: the period is the current UTC calendar month.
Get usage (canonical)
Get usage (legacy)
Prefer
GET /api/v1/tenants/me/usage for new integrations — the legacy endpoint’s field names predate MAD-based pricing.Console usage
GET /api/v1/tenants/me/usage, reachable with an API key as well as a session.
Authentication — Authorization: Bearer gpat_…/aat_… with the org:read scope, or a dashboard session (viewer+).
Tier limits
See also
- Billing
- Validate Attestation — the
quota_exceedederror when the MAD limit and grace period are exhausted