Explorium · Rate Limits

Explorium Rate Limits

Explorium DOES publish a numeric rate limit, contrary to the previous round's finding: 200 queries per minute per API key over a 60-second sliding window, with a full set of response headers and a documented 429 body. It is advertised as a first-class discovery target - the api-catalog linkset names the rate-limit page as the API's service-meta relation, which is a genuinely rare thing to do. The subtlety that matters is the counting rule: a query is an ENTITY, not an HTTP request, so one batch call carrying 50 businesses consumes 50 of the 200.

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

It captures 6 rate-limit definitions, measuring queries, entities, records, and credits.

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

Tagged areas include Data Enrichment, B2B Data, Web Intelligence, Rate Limiting, and Quotas.

6 Limits Throttle: 429
Data EnrichmentB2B DataWeb IntelligenceRate LimitingQuotas

Limits

Query Rate per-api-key
queries
200
The headline limit. Counters are independent per API key, so multiple keys on one account multiply available throughput.
Query Counting request
entities
Single-entity endpoints count one query per request. Bulk and batch endpoints count EACH ROW in the payload as a separate query - a 50-entity request consumes 50 queries. Batching saves round trips, not quota.
Sync Batch Size request
records
50
Match and bulk enrichment requests accept at most 50 records per call, returned in input order.
Async Job Size job
records
10000
Asynchronous enrichment jobs process up to 10,000 records, with a 24-hour runtime cap and 7-day result retention; result URLs expire after about an hour.
Pagination Depth request
records
60000
Offset-based pagination is capped at 60,000 records with a maximum page_size of 500. Cursor-based (search_after) pagination has no cap.
Credit Pool account
credits
per package
Orthogonal to the rate limit. Exhaustion returns 403 with "You have insufficient credits", not 429. See plans/explorium-plans-pricing.yml.

Policies

Entity-based counting
A query is an entity, not a request. This is the single most misread part of Explorium's throttling contract and the provider calls it out as a gotcha in its own published Agent Skill.
Backoff strategy
Implement exponential backoff and honour Retry-After on 429. Explorium's published guidance is to avoid parallel requests that might exceed the limit and to never retry a 4xx without fixing the cause.
Preemptive throttling
Throttle client-side once X-RateLimit-Remaining falls below 10.
Enterprise uplift
"Additional queries per minute" is an explicitly listed Enterprise plan entitlement on the published pricing page, so 200/min is the standard-tier ceiling rather than a platform ceiling.

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/explorium-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.