Explorium · Rate Limits

Explorium Rate Limits

Explorium does not publish fixed numeric per-minute request limits for the AgentSource API. Usage is governed primarily by the shared credit pool rather than a request-rate cap - each match, fetch, enrichment, and event action draws credits, and calls stop when the balance is exhausted or expired. Batch-oriented endpoints impose an explicit structural limit: match and bulk enrichment requests accept at most 50 records per call. Numeric throttling thresholds are not documented as of the review date.

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 4 rate-limit definitions, measuring requests, credits, and records.

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

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

4 Limits Throttle: 429
Data EnrichmentB2B DataWeb IntelligenceRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented for the AgentSource API.
Credit Pool account
credits
per package
Usage is metered against a shared prepaid credit balance; calls fail when credits are exhausted or expired.
Match Batch Size request
records
50
Match endpoints accept up to 50 businesses or prospects per call, returned in input order.
Bulk Enrichment Batch Size request
records
50
Bulk enrichment endpoints process up to 50 records per request.

Policies

Credit Metering
All match, fetch, stats, enrichment, and event calls draw from a single shared credit pool that meters usage in place of a hard request cap.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources