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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

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 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 Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/zenscrape-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.