Rate Limits
Rate limits are based on your Enigma account's plan. All queries count towards the rate limit regardless of the query type.
KYB API Rate Limits
KYB API rate limits vary by plan and contract. Contact Enigma support to confirm the limits for your account.
A 429 Too Many Requests response is returned when you exceed a rate limit. Use exponential backoff starting at 1 second and doubling on each retry, up to a maximum of 60 seconds.
GraphQL API Rate Limits
The Enigma GraphQL API has the following rate limits:
| Plan | Rate Limit (RPS) | Burst Limit | Daily Limit (RPD) |
|---|---|---|---|
| Trial | 10 | 20 | 100,000 |
| Pro | 50 | 100 | 500,000 |
| Max | 50 | 100 | 500,000 |
| Enterprise | 100 | 200 | No limit |
A 429 Slow Down response code is returned if you hit a rate limit.
Handling 429 Responses
Every 429 response includes a Retry-After header set to the number of seconds to wait before retrying. Read this header and wait at least that long — do not guess a retry interval.
Best practices:
- Respect
Retry-After: treat it as the minimum wait, not a suggestion. Retrying sooner extends the throttling window. - Use backoff for repeated
429s: if you hit a429again after honoringRetry-After, back off further (for example, double the wait) instead of retrying at the same interval. - Check which limit you hit: a
429can come from the per-second rate limit, the burst limit, or the daily limit (see the table above). If you've exhausted your daily limit,Retry-Aftermay point past the point where retrying makes sense within the same day — check your request volume before retrying in a loop. - Smooth out bursts: client-side request queuing or a token-bucket limiter set below your plan's RPS keeps you under the burst limit instead of alternating between full speed and
429s. - Don't retry blindly: cap total retries per request and surface the failure if
429s persist — a tight retry loop that always retries can mask a client misconfiguration (for example, requesting far more RPS than your plan allows).
MCP Tool Call Rate Limits
Each MCP tool has both daily and monthly rate limits:
- Daily rate limits are calculated on a rolling 24-hour window basis.
- Monthly rate limits are calculated on a rolling 30-day window basis.
Tool rate limits are independent of each other - hitting the rate limit for one tool does not impact utilization of other tools.
When a tool hits a rate limit, it returns a 429 Slow Down response code.
Pro plan limits
| Tool | Daily Limit (RPD) | Monthly Limit (RPM) |
|---|---|---|
search_business | 500 | 8000 |
search_person | 500 | 8000 |
get_brand_locations | 500 | 8000 |
get_brand_legal_entities | 500 | 8000 |
get_brand_card_analytics | 500 | 8000 |
search_gov_archive | 500 | 6000 |
generate_brands_segment | 100 | 1000 |
generate_locations_segment | 100 | 1000 |
search_kyb | 100 | 2000 |
search_negative_news | 100 | 2000 |
Max plan limits
| Tool | Daily Limit (RPD) | Monthly Limit (RPM) |
|---|---|---|
search_business | 500 | 8000 |
search_person | 500 | 8000 |
get_brand_locations | 500 | 8000 |
get_brand_legal_entities | 500 | 8000 |
get_brand_card_analytics | 500 | 8000 |
search_gov_archive | 500 | 6000 |
generate_brands_segment | 100 | 1000 |
generate_locations_segment | 100 | 1000 |
search_kyb | 100 | 2000 |
search_negative_news | 100 | 2000 |
Enterprise Plan Limits
Enterprise plan rate limits are configurable based on your organization's needs. Please contact us to discuss your needs.