ZenRows
A scraping API billed from one credit balance, where JavaScript rendering costs five credits and residential bandwidth draws 25,000 per gigabyte.
Plan prices
Not published here. ZenRows sells monthly tiers with a credit allowance rather than a bandwidth ladder, and its tier names cannot be read reliably from the page — they come back joined to the button beside them. We would rather show nothing than a plan named wrongly at a price that is right.
What is above is what we can state: the unit the plan is billed in, and what one unit of work costs. Those are the numbers that decide the bill on a per-request product.
Nothing yet, we'll log every price and policy move we spot.
Whose network is underneath
Not established
A scraping API is a storefront over somebody’s proxy pool. This one does not say whose. We looked twice: through its pricing, about and FAQ pages, and then through the places a supplier has to be named for data-protection reasons — subprocessor, trust, security and privacy pages. Neither names a network. That is not the same as there being no upstream.
It matters because ethics do not stop at the vendor boundary. In July 2026 the FBI seized a residential proxy platform built on roughly two million consumer devices enrolled with little or no meaningful consent, and that network was resold under other brands. A clean storefront can sit on top of one.
- Billed in
- credits
- Failed requests
- Not charged
- Concurrent requests
- 5
- JavaScript rendering
- Offered
What one unit of work costs
A credit is not a price until you know what it buys, and the same plan charges different amounts for different work.
- javascript rendering
- 5 credits
- residential bandwidth
- 25,000 credits
Keep comparing
- Where ZenRows says its addresses come from they do not say, and what that means
- Cost calculator, what ZenRows actually costs at your monthly volume