Axiom · Rate Limits

Axiom Co Rate Limits

Axiom applies three distinct categories of API limit and communicates each through its own set of response headers. General API rate limits cap requests per minute at either the user or organization scope. Query limits are metered in gigabyte-milliseconds (GB*ms) of query compute against your plan. Ingest limits are metered in bytes per month against your plan, and Axiom additionally monitors ingest request rate - an organization sending an excessive, sustained number of requests per second far above normal usage may have its ingest suspended to protect system stability. When any limit is exceeded the API returns HTTP 429 Too Many Requests with a JSON body of {"message": "rate limit exceeded"}. Axiom recommends batching clients to aggregate events and reduce request rate.

Axiom Co Rate Limits is the machine-readable rate-limit profile for Axiom on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, gb_milliseconds, bytes, and requests_per_second.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and throttledBody.

Tagged areas include Observability, Log Management, Event Data, Rate Limiting, and Quotas.

4 Limits Throttle: 429
ObservabilityLog ManagementEvent DataRate LimitingQuotas

Limits

General API Requests user-or-organization
requests
per-minute (surfaced in X-RateLimit-Limit)
Applies to standard REST API operations; scope reported in X-RateLimit-Scope.
Query Compute organization
gb_milliseconds
per plan (surfaced in X-QueryLimit-Limit)
APL and legacy queries consume query compute measured in GB*ms against the plan.
Ingest Volume organization
bytes
per month per plan (surfaced in X-IngestLimit-Limit)
Monthly data-loaded allowance; overage and rates depend on plan tier.
Ingest Request Rate organization
requests_per_second
monitored (no fixed published constant)
Sustained excessive requests-per-second far above normal usage may lead to ingest suspension. Use batching clients to aggregate events.

Policies

Batching
Axiom recommends batching clients that aggregate events before sending to stay within ingest request-rate expectations and reduce 429s.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and read the X-RateLimit-Reset / X-QueryLimit-Reset / X-IngestLimit-Reset headers to time retries.
Header-Driven Throttling
Remaining allowance for each category (general, query, ingest) is exposed in dedicated response headers so clients can self-throttle before hitting 429.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/axiom-co-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.