Rate Limits

Overview

AgentScore applies rate limits per API key to ensure fair usage and API stability. Limits vary by plan tier and endpoint.

Tier	Reputation (single)	Reputation (batch)	Stats / Health
Free	60 req/min	Not available	60 req/min
Starter	300 req/min	30 req/min	120 req/min
Growth	600 req/min	60 req/min	120 req/min
Scale	1,200 req/min	120 req/min	120 req/min
Enterprise	Custom	Custom	Custom

In addition to per-minute rate limits, each plan includes a monthly call allowance:

Batch requests count as one call per address in the batch.

Every response includes rate limit headers:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed in the current window
`X-RateLimit-Remaining`	Requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp when the window resets

When you exceed the rate limit, the API returns:

HTTP/2 429 Too Many Requests

{
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded. Try again in 12 seconds."
  }
}

The Retry-After header indicates how many seconds to wait before retrying.

Cache responses — Reputation scores change slowly. Cache results for the ttl_seconds value returned in each response (60-300 seconds depending on tier).
Use batch for bulk lookups — A single batch request is more efficient than many individual calls.
Monitor usage — Check your remaining quota from the dashboard or response headers.
Implement backoff — On 429 responses, wait for the Retry-After duration before retrying.

Legacy endpoints (/api/v1/x402/*, /api/v1/erc8004/*) have separate rate limits: