Zenscrape · Rate Limits

Zenscrape Rate Limits

Zenscrape governs usage through two mechanisms: a monthly request-credit quota tied to the subscription tier, and a concurrent-request ceiling that scales by plan (10 on Small, 25 on Medium, 50 on Large, 100 on Professional). Each scrape consumes 1 to 25 credits depending on whether rendering and/or premium proxies are used. Exhausting credits or exceeding concurrency results in throttling rather than per-minute request caps.

Zenscrape Rate Limits is the machine-readable rate-limit profile for Zenscrape on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring credits and concurrency.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Web Scraping, Proxy, HTML, Data Extraction, and JavaScript Rendering.

3 Limits Throttle: 429
Web ScrapingProxyHTMLData ExtractionJavaScript RenderingRate LimitingQuotasThrottling

Limits

Monthly Request Credits account
credits
1000-5000000 by plan
Free 1,000; Small 250,000; Medium 1,000,000; Large 3,000,000; Professional 5,000,000.
Concurrent Requests account
concurrency
10-100 by plan
Small 10, Medium 25, Large 50, Professional 100; Free tier not published.
Per-Request Credit Cost request
credits
1-25 per request
1 basic, 5 render, 10 premium, 25 premium + render.

Policies

Quota Exhaustion
Requests are rejected once the monthly credit allotment is consumed; upgrade the plan or wait for renewal.
Concurrency Ceiling
Requests above the plan's concurrent limit are throttled; clients should queue and retry with backoff.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on throttling.

Sources