Skip to main content
ScrapeGraphAI enforces rate limits to ensure reliable performance for all users. Limits vary by plan.

Limits overview

For full pricing details, see Plans & Pricing.
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 minute
  • X-RateLimit-Remaining — requests remaining in the current window
  • X-RateLimit-Reset — Unix timestamp when the limit resets

Handling the 429 response

When you exceed the rate limit, the API returns HTTP 429 Too Many Requests. In the v2 SDK this surfaces as res.status === "error" — the SDK does not raise. Retry with exponential backoff:
See the rate limiting troubleshooting guide for a JavaScript example and more tips.

Increasing your limits

  • Upgrade your plan from the dashboard to get higher limits immediately.
  • Enterprise customers can request custom rate limit configurations by contacting support.