scrapeprices 
Zenscrape
Zenscrape prints two different prices for the same thing. On its documentation page the credit-cost table says a premium (residential) request costs 10 credits, and the parameter table six inches below says premium "counts as 20 credits towards your quota". Both were read on the same URL on the same day, and nothing reconciles them, so the cheaper figure is recorded and the expensive one is on the record too. The rest is a conventional 1 / 5 / 10 / 25 ladder on plans from $59.99 for 250,000 credits, which is roughly twice what ScrapeOwl charges for the same credit volume with the same multipliers. Other things a buyer would want: the pricing page is the homepage, because zenscrape.com/pricing/ is a noindexed 404; the documentation subdomain the older links point at is a dead 522, with the real docs now on app.zenscrape.com; and the free card says "1,000 Searched" where every other card says Credits. Failures are not clearly free - the FAQ says only that CAPTCHA-related errors are "usually not deducted" and offers to refund them on request, which is a support promise, not a billing rule. Zenscrape and Scrapestack are both APILayer products under Idera, and their price lists do not match.
Plain page, by volume
| Pages per month | Monthly bill | Per 1,000 | Cheapest route | Allowance unused |
|---|---|---|---|---|
| 1k | $59.99 | $59.99 | Small | 249,000 units |
| 10k | $59.99 | $6.00 | Small | 240,000 units |
| 100k | $59.99 | $0.600 | Small | 150,000 units |
| 1M | $99.99 | $0.100 | Medium | - |
How Zenscrape compares
At 10,000 pages a month Zenscrape costs $6.00 per 1,000, 46.1x the cheapest published route and 8.6x AnyAPI.
| Provider | 1k a month | 10k a month | 100k a month | 1M a month |
|---|---|---|---|---|
Z  Zyte API | $0.130 | $0.130 | $0.130 | $0.100 |
A  AnyAPI | $0.700 | $0.700 | $0.700 | $0.700 |
W  WebScrapingAPI | $19.00 | $4.90 | $1.49 | no plan reaches this volume |
| Z Zenscrape | $59.99 | $6.00 | $0.600 | $0.100 |
List prices, dollars per 1,000 Plain pages at the cheapest published route to each volume. How this is worked out
Every published plan
| Plan | Price | Included credits | Overage each | Note |
|---|---|---|---|---|
| Free | $0 per month | 1,000 | not published | "$0 /mo", "1,000 Searched". No concurrency, geotargeting, standard-proxy or premium-proxy line items are listed on this card, unlike every paid card. |
| Small | $59.99 per month | 250,000 | not published | 250,000 credits, 10 concurrent requests, worldwide geotargeting, standard proxies, premium proxies, self-service onboarding. No SLA on this tier. No overage rate is published on any tier. |
| Medium | $99.99 per month | 1,000,000 | not published | 1,000,000 credits, 25 concurrent, concierge onboarding, first tier with a Service Level Agreement. |
| Large | $250 per month | 3,000,000 | not published | 3,000,000 credits, 50 concurrent, Service Level Agreement. |
| Professional | $350 per month | 5,000,000 | not published | 5,000,000 credits, 100 concurrent, Service Level Agreement, prioritized queue. |
| Custom quote | on request | - | not published | Verbatim: "Need More Credit? Contact us for a quote! We will reply within a few hours." No public price. |
Zenscrape contradicts itself on the residential price, on one page, in two tables. The "Credit Costs & Failed Requests" summary table gives premium=false render=false 1, premium=false render=true 5, premium=true render=false 10, premium=true render=true 25. The parameter table on the same page says premium is "optional, boolean, counts as 20 credits towards your quota" while render is "optional, boolean, counts as 5 credits towards your quota". So premium alone is 10 in one table and 20 in the other. The lower figure is recorded because it is the one in the table headed Credit Costs, and the discrepancy is flagged in notes rather than resolved. Anti-bot is recorded at the same 10 as residential because there is no separate anti-bot tier or parameter: premium is described as the mode that "unlocks sites that are hard to scrape", and Cloudflare handling is claimed as automatic and unpriced ("Zenscrape automatically detects the presence of Cloudflare protection on websites, and more importantly, it takes proactive measures to handle it without any manual intervention required from your end"). Markdown is null: no markdown or output-format parameter exists. Page intro, verbatim: "a request can cost between 1 and 25 credits".
Cost by kind of fetch
Per 1,000, at 10,000 pages a month.
What it can do
Only what the provider's own pages state.
Where these numbers came from
- https://zenscrape.com/ read 2026-09-14 / The pricing table lives on the homepage at #pricingSection; zenscrape.com/pricing/ returns 404 and is noindexed. Cards verbatim: Free $0 /mo "1,000 Searched"; Small $59.99 /mo 250,000 Credits, 10 Concurrent Requests, Worldwide Geotargeting, Standard Proxies, Premium Proxies, Self-Service Onboarding; Medium $99.99 /mo 1,000,000 Credits, 25 Concurrent, Concierge Onboarding, Service Level Agreement; Large $249.99 /mo 3,000,000 Credits, 50 Concurrent, SLA; Professional $349.99 /mo 5,000,000 Credits, 100 Concurrent, SLA, Prioritized Queue; "Need More Credit? Contact us for a quote!". FAQ verbatim on annual: "Yes. We also offer you a 10% discount if you choose an annual subscription plan." FAQ verbatim on failures: "Will request errors be counted towards my monthly limit? This depends on the error code. Errors that are related to captchas are usually not deducted from your credit volume. If this happens anyway, please contact us and we will refund the lost credits back to your API key." FAQ on uptime: "an uptime of 99.9%, calculated in the past 12 months." Cloudflare claim: "Zenscrape automatically detects the presence of Cloudflare protection on websites, and more importantly, it takes proactive measures to handle it without any manual intervention required from your end." Footer: "(c) 2026 Zenscrape API, an APILayer product."
- https://app.zenscrape.com/documentation read 2026-09-14 / The credit table, and the contradiction. Section "Credit Costs & Failed Requests", verbatim intro: "The number of credits that is counted towards your quota depends on the type request configuration that and the status code that the API endpoint returns. Hence, a request can cost between 1 and 25 credits." Table: premium false / render false = 1; false / true = 5; true / false = 10; true / true = 25. Basic Usage: "adding the url parameter to your request will fetch the HTML content from the target website. This request configuration will use standard proxies and will count as 1 credit towards your monthly limit." But the parameter table on the SAME page says: "premium optional, boolean, counts as 20 credits towards your quota. Uses residential proxies, unlocks sites that are hard to scrape" and "render optional, boolean, counts as 5 credits towards your quota". 10 against 20 for the same flag, unreconciled. The page is a JavaScript application: it is empty to a plain fetch and had to be read in a browser. No statement anywhere that failed requests are free.
- https://documentation.zenscrape.com/ read 2026-09-14 / Rot evidence. The documentation subdomain Zenscrape's own older pages and third parties link to returns HTTP 522 (Cloudflare cannot reach the origin), not a redirect. The live docs are at app.zenscrape.com/documentation, linked from the homepage nav.
- https://zenscrape.com/imprint/ read 2026-09-14 / Ownership and country: the imprint link resolves to the Idera, Inc. / apilayer legal page, contact address "6805 N Capital of Texas Hwy, Suite 275, Austin, TX 78731 US". Same corporate parent as Scrapestack.
Something out of date? Send the provider's own page to hello@scrapeprices.com and it is corrected on the next capture.