Changelog · July 16, 2026
Per-project rate limits
A predictable ceiling, with a header that says when to try again.
By Roger Campos · Last updated: July 2026
TL;DR
The API is rate limited per project key: 60 requests a minute, with a burst ceiling of 15 per 10 seconds, on every plan. A request over the limit gets a 429 with a Retry-After header and a rate_limited body — distinct from running out of credits.
Free plan, no credit card. 1,000 credits a month.
The limit counts requests, not credits, and applies to every analysis endpoint including /scrape. Its 429 is rate_limited and carries Retry-After; the credits 429 is quota_exceeded, so a client can tell backing off for seconds from waiting for a new month.
Cache hits are cheap for you but still requests, so they count toward the rate limit. The MCP endpoint has its own limit: 300 calls per 5 minutes per token.
FAQ
Frequently asked questions
No. It is the same on every plan; paid plans run more requests in parallel instead.
Read the Retry-After header on the rate_limited response.
Per project key.
Try it on the free plan.
Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.