ScrapeGraphAI enforces rate limits to ensure reliable performance for all users. Limits vary by plan.Documentation Index
Fetch the complete documentation index at: https://docs.scrapegraphai.com/llms.txt
Use this file to discover all available pages before exploring further.
Limits overview
| Plan | Requests per minute | Concurrent crawls | Monitors | Monthly credits |
|---|---|---|---|---|
| Free | 10 | 1 | 1 | 500 |
| Starter | 100 | 3 | 5 | 10,000 |
| Growth | 500 | 15 | 25 | 100,000 |
| Pro | 5,000 | 50 | 100 | 750,000 |
| Enterprise | Custom | Custom | Custom | Custom |
Contact support for custom limits or high-volume plans.
What counts as a request?
Each API call to any v2 endpoint (/api/extract, /api/scrape, /api/search, /api/crawl, /api/monitor, …) counts as one request toward your rate limit. Polling a crawl or monitor status endpoint does not count toward the limit.
Rate limit headers
Every API response includes headers that show your current rate limit status:X-RateLimit-Limit— maximum requests allowed per minuteX-RateLimit-Remaining— requests remaining in the current windowX-RateLimit-Reset— Unix timestamp when the limit resets
Handling the 429 response
When you exceed the rate limit, the API returns HTTP429 Too Many Requests. In the v2 SDK this surfaces as res.status === "error" — the SDK does not raise. Retry with exponential backoff: