scrapeprices 
WebScrapingAPI
One of the two providers here whose own pages disagree with each other. The current Scraper API pricing page sells a flat monthly allowance of plain requests - $19 for 7,000 up to $599 for 450,000 - with JavaScript rendering, country targeting, anti-bot handling and auto parsing marked Included on every tier and no multiplier printed anywhere; the word credit never appears on it. The still-live quick-start guide describes the same product as metered in API credits, on Starter and Grow plans that no longer exist, and the two docs pages that once carried the proxy and stealth multipliers now 404. So a rendered page costs the same as a static one on today's page, and that is what is recorded, but it rests on the absence of a multiplier rather than on a statement that there is none. The residential and anti-bot cells are empty for a different reason: the product is sold, but the only residential price WebScrapingAPI publishes is $8.50 per gigabyte of proxy traffic on a separate product, and a gigabyte is not a page. The one genuinely good disclosure is also in the legacy guide: only status 200 responses are charged, and a request that times out after 10 seconds is free.
Plain page, by volume
| Pages per month | Monthly bill | Per 1,000 | Cheapest route | Allowance unused |
|---|---|---|---|---|
| 1k | $19.00 | $19.00 | Starter | 6,000 units |
| 10k | $49.00 | $4.90 | Basic | 10,000 units |
| 100k | $149 | $1.49 | Advanced | - |
| 1M | no plan reaches this volume | - | - | - |
How WebScrapingAPI compares
At 10,000 pages a month WebScrapingAPI costs $4.90 per 1,000, 37.7x the cheapest published route and 7.0x 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 |
S  ScraperAPI | $49.00 | $4.90 | $0.490 | $0.149 |
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 requests | Overage each | Note |
|---|---|---|---|---|
| Trial | $0 per month | 5,000 | not published | $0 to start, 5,000 requests, 5 concurrent. Includes JavaScript rendering, all geographies, proxy rotation and anti-bot handling, auto parsing. |
| Starter | $19.00 per month | 7,000 | not published | 7,000 requests, 20 concurrent. No overage rate is published on any tier. |
| Basic | $49.00 per month | 20,000 | not published | 20,000 requests, 20 concurrent. |
| Standard | $99.00 per month | 45,000 | not published | 45,000 requests, 50 concurrent. First tier with premium support. |
| Advanced | $149 per month | 100,000 | not published | 100,000 requests, 100 concurrent. |
| Premium | $249 per month | 180,000 | not published | 180,000 requests, 200 concurrent. |
| Pro | $599 per month | 450,000 | not published | 450,000 requests, 500 concurrent, account manager. |
| Production review | on request | - | not published | Contact-us tier. FAQ verbatim: "Bring the target mix, volume, concurrency, rendering profile, and support needs to a production review for a plan aligned with that workload." No public price. |
The current pricing page counts plain requests, not credits: the allowance is labelled "requests" and "API calls" and the word credit does not appear on it at all. JavaScript rendering is 1 because the plan comparison table marks "JavaScript rendering: Included" on all seven tiers with no surcharge printed, and the docs' full-JSON example returns "cost": 1. Residential and anti-bot are null, not zero: the table sells "Proxy rotation and anti-bot handling: Included" on every tier but publishes no multiplier for it, the Scraper API has no premium, residential or stealth parameter (only render_js, country, state, city and asn), and the two docs pages that used to carry those multipliers - advanced-api-features/proxies and advanced-api-features/stealth-mode - now return 404. Residential IPs are sold instead as a separate product priced per gigabyte, from $8.50/GB with monthly plans from $52, which is not a per-page rate and is not converted here. Markdown is null because there is no markdown or output-format parameter in the API reference at all. A caveat: the still-live quick-start guide contradicts the pricing page, describing the allowance as "API credits" on plan names that no longer exist.
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://www.webscrapingapi.com/pricing/scraper-api read 2026-09-14 / Plan cards Trial $0/5,000, Starter $19/7,000, Basic $49/20,000, Standard $99/45,000, Advanced $149/100,000, Premium $249/180,000, Pro $599/450,000, all labelled "requests". Comparison table rows: API calls 5,000 / 7,000 / 20,000 / 45,000 / 100,000 / 180,000 / 450,000; concurrent requests 5 / 20 / 20 / 50 / 100 / 200 / 500; "JavaScript rendering: Included", "Country-level targeting: All geographies", "Proxy rotation and anti-bot handling: Included" and "Auto parsing: Included" on every tier. Searched the full page body: the words credit, annual, yearly, discount, SLA, uptime, failed and stealth do not appear. Footer of the site: "(c) 2026 Everything Data Solutions SRL. WebScrapingAPI is a commercial brand."
- https://www.webscrapingapi.com/pricing read 2026-09-14 / Product overview: "Scraper API: Start free with 5,000 requests, Paid plans start at $19 per month"; SERP API from $28/month; Amazon Data API from $59/month; "Residential Proxies: From $8.50 per GB, Monthly plans start at $52"; Managed Data from $299/month. The residential figure is per gigabyte of traffic, not per page, and is deliberately not converted into a per-page rate.
- https://www.webscrapingapi.com/web-scraping-api-quick-start-guide read 2026-09-14 / The contradiction. This page is still live and still says the allowance is credits, on plan names that no longer exist: "Starter plan, with up to 100,000 API credits", "Grow plan, with up to 1,000,000 API credits". It is also the only page that states the failure policy, verbatim: "One of the most important aspects that you have to know about response codes is that we only charge for successful responses. So if your request results in anything other than status code 200, you won't be charged", and "By default, we terminate a request (and not charge if failed) after 10s." Neither the pricing page nor the current docs repeat any of this.
- https://docs.webscrapingapi.com/webscrapingapi/getting-started/api-parameters read 2026-09-14 / Full parameter list: api_key, url, method, body, render_js, country, state, city, asn, timeout, extract_rules, json_response, json_dom, async, snapshot_id. There is no proxy_type, premium, residential, stealth_mode, device or markdown parameter. async "Set to true to queue the scrape and retrieve the finished result later" is the batch route; extract_rules is the parser.
- https://docs.webscrapingapi.com/introduction/custom-response-headers read 2026-09-14 / Credits exist as a concept but are never priced: "[PREFIX]-Call-Credit-Usage: Credit usage for the current request" and "[PREFIX]-Current-Credit-Usage: Total credit usage after the request". The full-JSON response page documents a "cost" integer, "Credit cost for the request", with 1 as its only example. Searching the docs for billing returns "No results found", and the legacy multiplier pages advanced-api-features/proxies and advanced-api-features/stealth-mode both return 404.
- https://docs.webscrapingapi.com/residential-proxies/getting-started read 2026-09-14 / "Residential Proxies route your requests through real residential IP addresses instead of datacenter IPs" and "Residential Proxies expose proxy endpoints that your own HTTP client uses as its outbound proxy" - a separate per-gigabyte product, not a mode of the Scraper API, and no credit multiplier.
Something out of date? Send the provider's own page to hello@scrapeprices.com and it is corrected on the next capture.