Scraping API PricesAll products / Scrape.do
Scrape.do pricing
How Scrape.do bundles proxy and rendering modes into successful-request credit costs, what remains unknown, and who fits.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Scrape.do counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
Scrape.do does not bill failed fetches, so failures cost nothing here.
- × 5
What the meter counts
500,000 credits
One attempt is not one billed unit here: this workload multiplies by 5 before any money is involved.
- =
Cash per month
$99.00 /mo
Pro. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 500,000 credit → Pro $99.00/mo = $0.99 per 1,000 pages kept
Every Scrape.do plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Hobby | $29.00 | n/a | n/a | 250,000 credit | 10 |
| Pro your job | $99.00 | n/a | n/a | 1,250,000 credit | 50 |
| Business | $249.00 | n/a | n/a | 3,500,000 credit | 100 |
| Advanced | $699.00 | n/a | n/a | 10,000,000 credit | 200 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.basic | 1 credit | request | source |
| request.js_render | 5 credit | request | source |
| request.residential_proxy | 10 credit | request | source |
| request.mobile_proxy | 10 credit | request | source |
| target.amazon | 1 credit | request | source |
| target.google | 10 credit | request | source |
| request.ai_extraction | 25 credit | request | source |
What Scrape.do does not publish
- The complete live per-domain default-cost table was not obtainable from the public page.
- The free allowance renewal period was not stated in the loaded pricing text.
- No public affiliate terms were obtainable.
What Scrape.do is
Scrape.do provides a general web scraping API and a separate set of ready-made APIs for named targets such as Google, Amazon, YouTube, Maps, Shopping, Flights, Hotels, News, Trends, and ChatGPT. The general endpoint handles proxy rotation, headers, JavaScript rendering, interactions, and blocking countermeasures, while ready-made endpoints return parsed JSON for supported targets. It is for developers who want either page retrieval or a predefined target schema without operating browser and proxy infrastructure. Source: Scrape.do product page, retrieved 2026-07-26.
ScraperAPI, ScrapingBee, and ZenRows are the nearest named comparisons. All three sell managed page retrieval, but Scrape.do’s relevant distinction is its explicit replacement bundles for proxy and rendering modes alongside target-specific ready APIs. This means the buyer chooses a documented request class instead of assuming every feature creates an independent additive fee. Sources: ScraperAPI pricing, ScrapingBee pricing, ZenRows pricing, and Scrape.do request costs, retrieved 2026-07-26.
How billing works
One unit is a credit, but one successful request can consume different numbers of credits. A basic datacenter request is the base class. JavaScript rendering, residential or mobile routing, combined proxy-and-rendering modes, AI extraction, and ready-made targets select higher published request bundles. Per-domain server defaults can override the requested mode, and the response cost header reports the observed charge. Billable responses include HTTP 2xx, 400, 404, and 410; other failed or blocked responses are not charged. The common buying mistake is to price from the parameter sent by the client rather than the bundle Scrape.do actually applies to that domain. Source: Scrape.do request-cost documentation, retrieved 2026-07-26.
What Scrape.do does not publish
- A complete live table of every domain-specific default and its resulting bundle cost. Source reviewed: request-cost documentation, retrieved 2026-07-26.
- The renewal period for the free allowance in the readable pricing text. Source reviewed: Scrape.do pricing, retrieved 2026-07-26.
- Effective annual plan amounts. The page directs buyers to support for annual discounts. Source reviewed: Scrape.do pricing, retrieved 2026-07-26.
Who it suits
Scrape.do suits teams that can inspect the returned cost header and want general retrieval plus ready-made target APIs in one account. It is less suitable when procurement must know every domain’s exact credit class before testing, or when the buyer assumes a requested low-cost mode cannot be upgraded by server defaults. The reason is that the bundle rules are published, but the domain-level selection table is not complete in the public material. Sources: Scrape.do, pricing, and request costs, retrieved 2026-07-26.
Answer
Scrape.do costs $99.00 for 100,000 JavaScript-rendered pages on its Pro offer. Every figure is sourced and dated.
Recorded 2026-07-26 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.