Reference
Rate limits
How many calls an address can make, and how to tell where it stands.
The free tools are open to anyone, so each address is limited to 60 calls a minute across MCP and REST. Calls made with an API key are limited per key instead, to 600 a minute.
Every answer says where you stand:
| Header | Meaning |
|---|---|
RateLimit-Limit |
Calls allowed in a minute |
RateLimit-Remaining |
Calls left in this minute |
RateLimit-Reset |
Seconds until the minute starts again |
Retry-After |
On a 429 only: seconds to wait |
A call over the limit gets 429 with the error code rate_limited over REST, or JSON-RPC error -32000 over MCP.
Over MCP, a JSON-RPC batch may hold at most 20 messages, and every tool call inside it counts as one call.
Staying under it
- Cache. Signals and ideas change once a day. Reading them once and keeping them is enough.
- Narrow. Use
query,heat,verdictandlimitinstead of reading everything and filtering yourself. - Back off. On a
429, wait forRetry-Afterbefore trying again.
For a higher limit, use an API key.