Skip to main content
GET
cURL
Read this before you start a polling loop or a batch job, so you know how much budget is left. Reading it spends nothing: it does not count against the per-minute limit, the monthly quota, or the daily total. A valid credential can read it after paid data access has lapsed.

Key response fields

Every authenticated response carries the same three monthly numbers in the X-Monthly-Quota-Limit, X-Monthly-Quota-Remaining, and X-Monthly-Quota-Reset headers. Once binding is true, any request past ceiling answers 429 rate_limited with error.reason monthly_quota_exceeded and a Retry-After to the month’s reset.

Example

What it does not return

  • Unlimited reads. This route shares a budget of 100 reads a minute per account with Account identity. Past that you get 429: wait Retry-After seconds, then send one request.
  • A paid data response. A lapsed credential still gets this diagnostic, while the paid data routes answer 402 subscription_required until the subscription is renewed.
  • A breakdown per endpoint. All three counters cover the whole account.
  • A guessed number. When the usage totals cannot be read you get 503 with Retry-After, or 500, never a zero.
  • An answer for an OAuth grant without the usage scope. That answers 403 insufficient_scope and names the missing scope.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict

Response

Usage budget and counters for the authenticated API key owner.

object
string
required
Allowed value: "usage"
data
object
required
meta
object
required