Scraping API PricesScrape.do vs ScraperAPI
The plan-step boundaries between two credit-priced general scraping APIs.
Scrape.do
ScraperAPI
The difference
Both paths, one ruler
Scrape.do
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.
ScraperAPI
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
ScraperAPI does not bill failed fetches, so failures cost nothing here.
- × 10
What the meter counts
1,000,000 credits
One attempt is not one billed unit here: this workload multiplies by 10 before any money is involved.
- =
Cash per month
$149.00 /mo
Startup. 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.
Both ladders share one linear scale, topping out at 1,000,000 counted units, so a longer bar means more billed work rather than a different drawing.
These figures are for one stated workload: 100,000 JavaScript-rendered pages a month at a 95% success rate. The comparison below names where the answer changes.
Decision boundary: for basic datacenter requests, the recurring free plans tie through 1,000 credits a month. Scrape.do has the lower monthly plan cost from 1,001 through 3,500,000 requests. ScraperAPI is lower from 3,500,001 through 5,000,000, then Scrape.do is lower again from 5,000,001 through 10,000,000. The verdict flips because Scrape.do’s $249 Business plan reaches 3.5 million credits before jumping to $699, while ScraperAPI has a $475 five-million-credit step; at the next boundary, Scrape.do’s same $699 plan reaches ten million while ScraperAPI moves to $975. (Scrape.do pricing, ScraperAPI pricing, retrieved 2026-07-26)
That ladder applies only to one-credit requests. Scrape.do publishes replacement bundles of 5 credits for datacenter rendering, 10 for residential or mobile routing, and 25 for those proxy classes with rendering. ScraperAPI publishes 10 credits for JavaScript or premium proxy, 25 for their documented combination, and higher target-specific costs for Google, Bing, LinkedIn, and stealth modes. A workload mix can therefore cross at a much smaller URL count than the basic-request bands. (Scrape.do request costs, ScraperAPI credit costs, retrieved 2026-07-26)
Billing models side by side
Scrape.do sells a monthly successful-credit allowance. Hobby is $29 for 250,000 credits, Pro is $99 for 1.25 million, Business is $249 for 3.5 million, and Advanced is $699 for ten million. Basic datacenter retrieval consumes one credit, while proxy, rendering, named-target, and AI request classes consume larger replacement bundles. Per-domain defaults can select a more expensive class than the caller requested, and the response includes a cost header that reports the observed debit. (Scrape.do pricing, Scrape.do request costs, retrieved 2026-07-26)
ScraperAPI also sells monthly credits, but its ladder is $49 for 100,000, $149 for one million, $299 for three million, $475 for five million, $975 for 10.5 million, and $1,975 for 21.5 million. Hobby through Business stop when the allowance is exhausted. Scaling and larger plans advertise pay as you go, but the public page does not state its unit rate. Unused credits reset at the billing boundary. (ScraperAPI pricing, retrieved 2026-07-26)
Failure billing is not interchangeable. Scrape.do lists HTTP 2xx, 400, 404, and 410 responses as billable and excludes other failed or blocked responses. ScraperAPI normally charges HTTP 200 and 404, and its documentation describes a client-cancellation window that can still consume credits. Those are contract rules, not evidence about either vendor’s ability to retrieve a target. (Scrape.do request costs, ScraperAPI credit costs, retrieved 2026-07-26)
What each provides that the other does not
Scrape.do is the only one of this pair whose reviewed documentation exposes a per-response cost header and a public table of domain defaults that can automatically select residential, rendering, or custom infrastructure. It also publishes ready-made APIs for targets including Google, Amazon, Maps, Shopping, Flights, Hotels, Trends, and ChatGPT. (Scrape.do, Scrape.do request costs, retrieved 2026-07-26)
ScraperAPI is the only one of this pair whose reviewed meter lists screenshot requests, Bing and LinkedIn target costs, named Cloudflare, Turnstile, DataDome, and PerimeterX handling, plus sticky sessions without an extra credit charge. Its public self-serve ladder also extends beyond Scrape.do’s ten-million-credit Advanced plan before custom pricing is required. (ScraperAPI pricing, ScraperAPI credit costs, retrieved 2026-07-26)
Who should pick which
Pick Scrape.do in its lower bands when its documented request bundle and domain cost header fit the job. Pick ScraperAPI in the 3,500,001 to 5,000,000 basic-request band, or when its named target and screenshot modes remove integration work. Return to Scrape.do above five million basic requests if the workload remains within Advanced’s ten-million-credit allowance. Above that point, compare ScraperAPI’s published higher tiers with a Scrape.do custom quote rather than extending the $699 plan. (Scrape.do pricing, ScraperAPI pricing, retrieved 2026-07-26)
The unresolved edges are Scrape.do’s complete live domain-default table and ScraperAPI’s combination rule for target, bypass, screenshot, and rendering costs. ScraperAPI’s pay-as-you-go unit rate is also unpublished. Test each production request shape and read the actual debit before committing to the headline URL count. (Scrape.do request costs, ScraperAPI credit costs, ScraperAPI pricing, retrieved 2026-07-26)