Zenrows Rate Limits
ZenRows throttles by plan-level concurrency caps and by per-feature request budgets (Basic, JS Rendering, Premium Proxy, Protected). Quota exhaustion and concurrency overflow are both returned as 429 with distinct ZenRows error codes (AUTH008 vs AUTH006). Every successful response surfaces the current concurrency state in dedicated response headers, and 402 responses signal budget exhaustion before traffic is throttled. There is no documented per-second request ceiling beyond the concurrency cap.
Zenrows Rate Limits is the machine-readable rate-limit profile for ZenRows on the APIs.io network, in the API Commons Rate Limits shape.
It captures 12 rate-limit definitions, measuring concurrent_requests, requests, and megabytes.
Limit state is signalled in the concurrencyLimit, concurrencyRemaining, requestCost, and requestId response headers.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 5 backoff/retry policies defined and response codes documented for concurrencyExceeded, rateLimited, quotaExceeded, featureNotInPlan, and subscriptionInactive.
Tagged areas include Web Scraping, Rate Limiting, and Concurrency.
concurrencyLimitconcurrencyRemainingrequestCostrequestId
generated, dated 2026-05-25.
Limits
Policies
Sources
- https://www.zenrows.com/pricing
- https://docs.zenrows.com/first-steps/pricing
- https://docs.zenrows.com/api-error-codes
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.