API key usage history + current quota
V2 Public API
GET /v2/me/usage
Current quota + paginated call history for the authenticated key.
GET
API key usage history + current quota
Auth: Required · Cost: Free (no quota debit) · Use case: Quota
visibility for self-service dashboards + pre-flight checks
user_api_usage, billing snapshot
from user_billing.
Use this endpoint to:
- Surface “X of Y calls remaining” inside your own admin UI.
- Detect quota exhaustion before firing a paid call (avoids a 402 round-trip).
- Audit which addresses your key has screened (CSV / SOC2 reporting).
Request
Response 200
billing object
When
monthly_quota is null, the user has not been onboarded onto a
paid plan yet. Calls will return 402 until the kabinet provisions a
plan.
rows[] — usage history
Each row mirrors one entry in user_api_usage.
Pagination
Errors
Notes
- This endpoint does not debit quota — call it as often as you like.
- Best-effort write semantics on
user_api_usage: in extremely rare cases (Supabase write fails) a paid call’s row may be missing. Billing is unaffected — it’s computed fromconsume_quotaon the hot path, not from this audit table. - For programmatic billing-period detection, also check
period_startchanges — when it increments, your monthly quota has reset.
See also
- V2 API key (auth) — how to issue + rotate
- V2 introduction — quota + refund semantics
- POST /v2/screen
— the typical paid call you’ll see in
rows[]
Authorizations
Your aeg_… API key from the dashboard (Account → API tab).
Query Parameters
Required range:
x >= 1Required range:
1 <= x <= 100ISO date; only rows with created_at >= since
Response
Successful Response
The response is of type Response Me Usage Me Usage Get · object.

