Introspect the calling key (whoami)
Return the identity the gateway resolved for your key: key_id, org_id, project_id, environment (test/live), status, the granted scopes, and the rate-limit/credit posture. Any active key may call it (no special scope), so it is the fastest way to self-diagnose a 403 insufficient_scope (check scopes), a 402 credit_exhausted/key_budget_exceeded (check credit and key_budget_cents), or an org_suspended (org_status).
Authorizations
Use Authorization: Bearer pyai_live_... (or pyai_test_...).
Response
The calling key's identity and limits.
The identity the gateway resolved for the calling key, plus its enforced limits and credit posture. Returned by GET /v1/me.
"identity"
The calling key's id.
"key_7f3a0b12"
"org_abc123"
"proj_abc123"
Key environment. test keys run in the sandbox tier (daily unit cap, no credit gate).
test, live Key status.
active, revoked Owning org status; suspended explains a 403 org_suspended.
active, suspended Granted scopes. A missing scope here explains a 403 insufficient_scope.
["voice:synthesize", "hear:transcribe"]
Key expiry (Unix ms); null = non-expiring.
Billing plan id.
"payg"
Per-key gateway limits (what the edge actually enforces).
Prepaid-credit posture. Explains a 402 credit_exhausted.
Per-key monthly spend cap (USD cents); null = no per-key budget. Hitting it is a 402 key_budget_exceeded.