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.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/zenscrape-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.