Best Scrape.do Alternatives in 2026: 8 Tools Compared
Last updated: November 11, 2026. Benchmark figures come from the October 30, 2026 run of the Web Data Frontier Benchmark. Pricing was checked against each vendor's published pages on October 27, 2026, and Bright Data's, Context.dev's and Oxylabs' again on November 11, 2026.
What is the best Scrape.do alternative?
String is the strongest pick when a web scraping API has to return protected pages: it passed 98.6% of requests (as of October 2026) on our 100-site benchmark, the highest of 17 providers. Scrape.do itself placed second at 94.0% in the October run. Choose Scrapfly for several APIs on one key, Context.dev for one flat credit per page with protection included, Firecrawl for crawl-to-content work, Bright Data for pay-as-you-go unblocking at scale, Oxylabs for news and finance lists, and Zyte for short responses at a price tier the vendor sets.
Scrape.do is a cheap, simple web scraping API: $99 buys 1,250,000 credits, and it bills only responses it counts as successful. The reasons to look elsewhere are specific: its pricing page claims 99.98% success with no stated method, while it passed 94.0% on our 100 sites; the credit cost of a page moves with the target and the mode; and it publishes no MCP server of its own.
TL;DR
- Scrape.do joined the benchmark in the October 30 run, through its own pull request to the harness. It passed 94.0%, or 470 of 500, second of 17, with a 5.08-second latency score, also second. Its pricing page claims a 99.98% success rate and does not say how that was measured.
- String passed 98.6% (as of October 2026), or 493 of 500, the highest of the 17 web scraping APIs tested. It returned all five attempts on 95 of 100 sites and at least one on all 100. Scrape.do returned all five on 91 and nothing on 3. Blocked requests are free and the first 20,000 standard fetches need no card.
- The surcharge list: Scrape.do's own per-domain price table names 8 of our 100 benchmark sites, at 10 to 30 credits a request. The 17 tested APIs averaged 62.4% on those 8 against 71.9% on the other 92. Only String returned every attempt on all 8; Scrape.do and Context.dev did on 7.
- Scrape.do bills 1 credit for a datacenter request and 25 for a residential request with a browser, per its request cost docs. A target's 400, 404 or 410 response counts as a success and is billed.
- On Pro, $99 a month, that is about $0.08 per 1,000 plain pages and $1.98 per 1,000 residential pages with rendering. LinkedIn costs 30 credits, about $2.38 per 1,000.
- Scrape.do's documentation lists n8n and Zapier integrations and no MCP server. All seven alternatives here publish one.
- Every benchmark number comes from a public harness that anyone can rerun with their own API keys.
Scrape.do and seven alternatives at a glance
| Provider | Best for | Benchmark success | Latency score | What about $100 a month buys (per 1,000) | The catch |
|---|---|---|---|---|---|
| String | Protected targets that must return content | 98.6% | 4.24s | Growth, $99: $0.16 for a plain fetch; $0.80 to $0.90 with a browser or a premium proxy; $3.25 with both. Blocked requests are free and credits roll over | More expensive than Scrape.do's rate card at every request type; no SOC 2 report yet |
| Scrape.do | A low credit price and a simple GET endpoint | 94.0% | 5.08s | Pro, $99: about $0.08 datacenter; $0.40 with rendering; $0.79 residential; $1.98 residential with rendering; more on listed domains | Returned nothing on temu.com, shop.lululemon.com and asda.com; a target's 404 is billed |
| Scrapfly | Several APIs on one key | 86.8% | 19.62s | Pro, $100: $0.10 datacenter; $0.50 with rendering or Unblocker; $2.50 on residential | Unblocker fees vary by target, and credits do not roll over |
| Context.dev | One flat credit per page, protection included | 93.0% | 10.96s | Pro, $90: 100,000 credits, or $0.90 per 1,000 pages | 6 sites returned nothing in the October run, mouser.com and ebay.com among them |
| Firecrawl | Crawl-to-content work and fast responses | 81.2% | 8.87s | Standard, $99 billed monthly: 100,000 credits, or $0.99 per 1,000 pages | A page that returns a 403 or 404 document still costs a credit |
| Bright Data | Pay-as-you-go unblocking at scale | 75.4% | 27.88s | No plan near $100. Pay as you go: $1.50 per 1,000 successful requests; Scale is $499 | Premium domains bill at a rate the pricing page does not list |
| Oxylabs | News and finance lists | 67.4% | 16.62s | Basic, $100: Web Unblocker at $6.00 per GB, up to 16 GB, or the /scrape endpoint at $0.90 per 1,000 results without JavaScript | The benchmarked product bills by bandwidth, so the cost per page depends on page size |
| Zyte | Short responses on a vendor-set price tier | 79.6% | 14.43s | $100 commitment: $0.10 to $0.95 per 1,000 HTTP responses; $0.75 to $12.00 with a browser | Zyte assigns the tier, and you cannot pick it |
Benchmark figures come from the October 30, 2026 run, with 500 requests per provider across 100 sites. The latency score is failure-aware: per target, the p75 of a provider's successful attempts; a provider with no successful attempt on a target inherits the p75 of the providers that succeeded, and a target nobody returned counts at the 90-second timeout. Scrape.do's per-1,000 prices are derived from its Pro plan, $99 for 1,250,000 credits, times its published credit cost per request type. Pricing comes from each vendor's published pages at the plan closest to $100 a month billed monthly.
Why people look at Scrape.do alternatives
Scrape.do sells a web scraping API: one GET call with a URL and a token, with proxy rotation, TLS fingerprinting, CAPTCHA handling and an optional headless browser behind it. It also runs a proxy mode, an async API for batch jobs, and ready-made scrapers for Amazon, Google, Walmart and a few other sites. The pricing page says every plan, including the free one, gets every feature, although it also lists premium residential proxies as a Business-plan item. For a small team that wants a cheap endpoint and little setup, that is a real reason to stay.
The case for moving rests on three things: results on hard sites, a bill that moves with the target, and agent support.
Hard sites
Scrape.do joined our benchmark in the October run. It passed 94.0% (as of October 2026), or 470 of 500, second of 17 providers, behind String's 98.6%. Its pricing page shows "99.98% Success rate" and gives no method, no site list and no date. On our 100 sites the 17 tested APIs ranged from 98.6% to 27.6%, so a rate means little without its site list. Scrape.do returned all five attempts on 91 sites, some attempts on 6, and nothing on 3: temu.com, shop.lululemon.com and asda.com. Its weakest anti-bot column was Akamai, at 87.0%, and its weakest vertical grocery and food, at 72.0%.
What Scrape.do also publishes is a list of the sites it treats as hard. Its request cost docs name 26 domains where it turns on residential proxies, a browser or a custom profile by default, and charges for it. Eight of those domains are in our benchmark, and the tested APIs did worse on them than on the rest, so Scrape.do's list and our data agree on direction. Scrape.do itself returned every attempt on seven of the eight. The section on the surcharge list below has the site-by-site results.
Pricing
Scrape.do's rate card is low. Pro costs $99 a month for 1,250,000 credits, about $0.08 per 1,000 credits, per its pricing page (checked October 27, 2026). A plain datacenter request costs 1 credit, a request with the headless browser 5, a residential or mobile request 10, and residential with the browser 25. On Pro that is about $0.08, $0.40, $0.79 and $1.98 per 1,000 pages.
The bill depends on the page. Protected sites need the residential and browser modes, which cost up to 25 times a plain request. On the listed domains Scrape.do applies its own profile "whether or not you also passed those parameters", from 10 credits for google.com to 30 for linkedin.com and 200 for sainsburys.co.uk. Four listed domains, including chewy.com and shopee, say "Contact support for access." The docs tell you to trust the Scrape.do-Request-Cost response header over the table.
Failure billing has one catch. The pricing FAQ says you "won't lose credits on timeouts, blocks, or errors." The request cost docs are more specific: "Status codes counted as successful: 2XX, 400, 404, 410." A target's 404 costs credits. In the October run, 16 of Scrape.do's 2xx responses were not the requested page; String returned none. When credits run out, requests stop until you upgrade or buy more, per the pricing FAQ. Annual billing takes two months off and is set up by hand through support.
Agent support
Scrape.do's documentation lists n8n and Zapier under integrations and no MCP server. A community package wraps its API, but Scrape.do does not publish or maintain one. All seven alternatives on this page publish their own.
How we tested these web scraping APIs
We ran 100 live sites, five attempts each, against 17 providers, for 500 requests per provider and 8,500 in all. Each provider ran through one adapter published in the repository. The timeout was 90 seconds. A request passed only when the response contained a marker from the real page, so a captcha interstitial returning HTTP 200 counted as a failure.
Scrape.do joined the harness through its own pull request, so its success and latency figures here are measured. Its prices still come from its own pricing page and docs.
Before the October run, the harness repaired six fixtures whose pages had changed: asda.com, autozone.com, marketwatch.com, cargurus.com, cars.com and temu.com. Each kept its site, anti-bot vendor and vertical. Scrape.do and Scrapfly take the proxy pool as a request parameter, and their adapters pin the top pool; Scrapfly's has pinned its residential pool since the harness moved five adapters to the settings their vendors document for bot-protected pages before the September run. Of the eight tools on this page, only String's adapter changed for October, and only to record the trace ID String returns; the request it sends is the same. We do not claim that every provider ran in its strongest anti-bot mode.
Disclosure: String built this benchmark and sells the product that ranks first in it. The answer to that conflict is a harness you can run yourself. The targets, pass criteria, and every provider configuration are open on GitHub, and the repository accepts your own API keys. The original benchmark post explains the pass rule and why the latency score refuses to reward fast failures.
Providers do contest results, and we publish the corrections. Firecrawl's engineer said its configuration was wrong, opened a pull request, and raised Firecrawl's score by 7.7 points. The October run keeps that corrected configuration.
Chart data
| Provider | Success rate | Passed | Latency score |
|---|---|---|---|
| String | 98.6% | 493/500 | 4.24s |
| Scrape.do | 94.0% | 470/500 | 5.08s |
| Context.dev | 93.0% | 465/500 | 10.96s |
| Scrapfly | 86.8% | 434/500 | 19.62s |
| ScrapingBee | 85.2% | 426/500 | 20.30s |
| Firecrawl | 81.2% | 406/500 | 8.87s |
| Zyte | 79.6% | 398/500 | 14.43s |
| Apify | 79.4% | 397/500 | 24.87s |
| ScraperAPI | 76.4% | 382/500 | 15.19s |
| Bright | 75.4% | 377/500 | 27.88s |
| Decodo | 71.2% | 356/500 | 28.29s |
| Nimble | 68.0% | 340/500 | 22.65s |
| Oxylabs | 67.4% | 337/500 | 16.62s |
| Browserbase | 43.0% | 215/500 | 18.01s |
| ZenRows | 41.8% | 209/500 | 21.91s |
| ScrapingAnt | 40.0% | 200/500 | 18.39s |
| Scrapingdog | 27.6% | 138/500 | 31.52s |
String vs Scrape.do: 98.6% against 94.0%, and a lower price card on Scrape.do's side
String's Web Access API makes one HTTP call against any URL. Proxy rotation, anti-bot handling, captcha solving and JavaScript rendering happen behind the endpoint.
Pricing. Usage-based rather than prepaid credits. Growth costs $99 a month (as of October 2026) and bills $0.16 per 1,000 fetch requests on a standard proxy, $0.90 on a premium proxy, $0.80 for a browser request on a standard proxy, and $3.25 with both. The first 20,000 standard fetches are free with no card, blocked requests are not billed, and unused credits roll over. Scrape.do's rate card is lower at every request type: about $0.08 against $0.16 for a plain page, and $1.98 for a residential page with a browser against $3.25 for a premium-proxy page with a browser.
Benchmark success. 98.6%, or 493 of 500, first of seventeen. String returned all five attempts on 95 sites and partial content on 5, and returned at least one attempt on all 100. Scrape.do passed 94.0%, or 470 of 500, second, with all five attempts on 91 sites and nothing on temu.com, shop.lululemon.com and asda.com.
Latency. String's latency score is 4.24 seconds, first of seventeen; Scrape.do's is 5.08 seconds, second. On the 14 sites all eight tools on this page returned in full, String's median was 1.10 seconds, the shortest of the eight, against Zyte's 1.50 and Scrape.do's 2.00.
Strengths. Coverage, measured in public. String returned all five attempts on all 8 sites on Scrape.do's surcharge list, the only tested API to do so. It passed 100% on the AWS WAF, Kasada, Fastly and no-named-vendor sites, 98.7% on Cloudflare and 97.0% on Akamai, where Scrape.do passed 87.0%. None of its 2xx responses was the wrong page.
Weaknesses. Price on the rate card. A team that already gets its pages from Scrape.do pays less there than on String at every request type. Scrape.do tied String on DataDome at 97.9% and beat it on PerimeterX, 100% against 97.8%. String passed 95.6% on news and finance, seventh of seventeen, where Scrape.do passed 100%, and 88.0% on grocery and food, with two of five on kroger.com. String is a narrower product than Scrape.do's ready-made Amazon and Google scrapers, and it has no SOC 2 report.
MCP. String ships a hosted MCP server for fetch, search and sitemap discovery, so an agent can call it without local setup.
Try it on your own list:
curl -X POST https://api.usestring.ai/v1/fetch \
-H "Authorization: Bearer $STRING_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.mouser.com/"}'
Scrapfly vs Scrape.do: two credit ladders, both measured
Pricing. As checked November 11, 2026, Pro is $100 a month for 1,000,000 credits. A datacenter scrape is 1 credit and a residential proxy is 25, per its billing docs, so plain and residential pages cost $0.10 and $2.50 per 1,000. The pricing page lists rendering or the Unblocker at 5 credits, while the Unblocker page says some target fees "are not publicly documented." Failed requests are not charged, with exceptions for several 4xx codes, 404 among them. Credits do not roll over. Scrape.do's card is lower: $0.79 against $2.50 for a residential page.
Benchmark success. 86.8%, or 434 of 500, fourth of seventeen, behind Scrape.do's 94.0%. It returned nothing on 5 sites, the third fewest after String and Scrape.do.
Latency. 19.62 seconds, tenth of seventeen. On the 14 sites all eight tools returned in full, Scrapfly's median was 4.80 seconds, sixth of eight.
Strengths. Scrapfly returned all five attempts on 3 of the 8 surcharge-list sites, four of five on four more, and three of five on mouser.com, the hardest of them. It passed 100% on news and finance, ticketing and developer sites, 97.1% on real estate, and 96.7% against AWS WAF. Scrapfly runs an MCP server.
Weaknesses. Speed, and a pricing model with more parts than Scrape.do's. Scrapfly returned nothing on temu.com, bestbuy.com, zara.com, alibaba.com and kroger.com, and passed 60.0% on the two search engines.
Context.dev vs Scrape.do: one flat credit, with protection included
Pricing. As checked November 11, 2026, Context.dev bills one credit per page, and per its pricing page JavaScript rendering, anti-bot bypass and proxies are included in the base scrape price. Developer costs $20 for 5,000 credits and Pro costs $90 for 100,000, or $0.90 per 1,000, with Pro overage at $2.00 per 1,000 credits. Per its credit docs, successful and partial results are charged, a request where every output fails is free, and a processed 404 costs credits. Against Scrape.do's $1.98 for a residential page with a browser, Context.dev's Pro rate is lower on protected pages and higher on plain ones.
Benchmark success. 93.0%, or 465 of 500, third of seventeen, one point behind Scrape.do. It returned all five attempts on 91 sites, some attempts on 3, and nothing on 6.
Latency. 10.96 seconds, fourth of seventeen. On the 14 sites all eight tools returned in full, Context.dev's median was 3.70 seconds.
Strengths. A predictable bill: the price of a page does not change with the site's protection. It passed 100% on the 19 DataDome sites, the only tested API to do so, and 100% on fashion, travel, review and local, and social sites. It returned every attempt on 7 of the 8 surcharge-list sites, linkedin.com, the most expensive of them, included. Context.dev runs a hosted MCP server, and its trust center lists SOC 2 Type II.
Weaknesses. Retail and Akamai. It passed 75.3% on retail and ecommerce and 79.0% against Akamai, and returned nothing on mouser.com, ebay.com, coupang.com, kroger.com, temu.com and buybuybaby.bedbathandbeyond.com. Our best web scraping tools page ranks it against the other hosted APIs.
Firecrawl vs Scrape.do: crawl-to-content, and fast
Pricing. As checked November 11, 2026, Standard is $99 a month billed monthly for 100,000 credits, or $0.99 per 1,000 pages. The pricing page defaults to the annual view at $83. Per its billing docs, a scrape that returns no document is free, while a page that comes back with an error status such as 403 or 404 costs a credit. Scrape.do also bills a target's 404, so the two share that rule. Credits roll over only on annual Scale and Enterprise.
Benchmark success. 81.2%, or 406 of 500, sixth of seventeen.
Latency. 8.87 seconds, third of seventeen behind String and Scrape.do. On the 14 sites all eight tools returned in full, Firecrawl's median was 5.60 seconds, seventh of eight.
Strengths. Speed, with crawl and extract next to scrape. It passed 100% (as of October 2026) on PerimeterX and Kasada and 98.7% on Cloudflare, tied with String for the top Cloudflare score. It has an open-source core and an MCP server.
Weaknesses. Social networks. Firecrawl returned nothing on reddit.com, linkedin.com, instagram.com, facebook.com, tiktok.com and pinterest.com, and passed 25.0% across the eight social sites, where Scrape.do passed 100%. It returned all five attempts on 6 of the 8 surcharge-list sites. Our Firecrawl alternatives page covers its other weak spots.
Bright Data vs Scrape.do: pay-as-you-go unblocking
Pricing. As checked November 11, 2026, no plan near $100. Web Unlocker pay as you go costs $1.50 per 1,000 successful requests, and Scale costs $499 a month for 383,000 requests. Bright Data bills successes only, with two caveats in its feature docs: premium domains bill at a higher rate that appears in the zone's estimated-cost panel and not on the pricing page, and a zone with custom headers or cookies enabled bills 100% of requests, successful and failed. The free tier is 5,000 credits a month, shared across Web Unlocker and its other APIs. Scrape.do publishes its per-domain prices; Bright Data does not.
Benchmark success. 75.4%, or 377 of 500, tenth of seventeen. It returned partial content on 40 sites.
Latency. 27.88 seconds, fifteenth of seventeen. On the 14 sites all eight tools returned in full, Bright Data's median was 9.90 seconds, the slowest of the eight.
Strengths. No commitment: pay as you go with no plan to size. It passed 94.3% on real estate, 93.3% on review and local sites and 86.7% against PerimeterX. On the surcharge list it returned every attempt on g2.com, linkedin.com and leboncoin.fr. Bright Data runs an MCP server.
Weaknesses. An unlisted rate on premium domains, a higher base price than Scrape.do's, and the slowest responses of the eight tools here. It returned nothing on 11 sites, including mouser.com, ticketmaster.com, reuters.com and indeed.com, and passed 45.0% on ticketing and 74.7% against DataDome. Our Bright Data alternatives page covers it in detail.
Oxylabs vs Scrape.do: news and finance, on a bandwidth bill
Pricing. The benchmark used Oxylabs Web Unblocker, which bills by bandwidth under one subscription that covers every Oxylabs product: Starter is $15 a month (as of November 2026) at $7.20 per GB, up to 2 GB, and Basic is $100 at $6.00 per GB, up to 16 GB. The cost per page depends on page size. Oxylabs also sells a Web API /scrape endpoint priced per result: on Basic, other sites cost $0.90 per 1,000 results without JavaScript and $1.40 with it. Its billing docs for the per-result scraper count every 2xx and 4xx response as billable, even when "the result doesn't contain expected information." The benchmark did not test the per-result API.
Benchmark success. 67.4%, or 337 of 500, thirteenth of seventeen.
Latency. 16.62 seconds, seventh of seventeen. On the 14 sites all eight tools returned in full, Oxylabs' median was 3.00 seconds, fourth of eight.
Strengths. 97.8% on news and finance, plus 100% against Kasada and 91.1% against PerimeterX. It returned all five attempts on 4 of the 8 surcharge-list sites. Oxylabs publishes an MCP server.
Weaknesses. Ticketing, where it returned nothing on all four sites, and a bandwidth bill that is hard to set in advance. It returned nothing on 26 sites, including mouser.com, g2.com, amazon.com and booking.com, and passed 16.7% against AWS WAF. The harness runs one general adapter per provider, and Oxylabs sells a dedicated Amazon endpoint that the run did not test. Our Oxylabs alternatives page compares it from the other side.
Zyte vs Scrape.do: short responses, on a tier Zyte sets
Pricing. As checked November 11, 2026, Zyte prices each site in five tiers. At the $100 monthly commitment, an HTTP response costs $0.10 to $0.95 per 1,000 and a browser response $0.75 to $12.00. Zyte assigns the tier automatically and reviews it quarterly with two weeks' notice. Unused commitment is not refunded. Bans and rate limits are free, but a target's 404 counts as a successful, billed response, as on Scrape.do. New accounts get a $5 credit for a 30-day trial. Both vendors price by how hard the site is; Scrape.do lets you pick the mode, and Zyte picks the tier.
Benchmark success. 79.6%, or 398 of 500, seventh of seventeen.
Latency. 14.43 seconds, fifth of seventeen. On the 14 sites all eight tools returned in full, Zyte's median was 1.50 seconds, second of eight behind String.
Strengths. Short responses on the sites it returns. Zyte passed 100% against Kasada and on news and finance, and 92.0% against Cloudflare. At its lowest HTTP tier, $0.10 per 1,000 is close to Scrape.do's $0.08. Zyte runs a remote MCP server.
Weaknesses. You cannot choose your rate, and the browser tier reaches $12.00 per 1,000. Zyte returned all five attempts on only 2 of the 8 surcharge-list sites, nothing on linkedin.com, and two of five on mouser.com. It passed 68.4% against DataDome and 70.0% against AWS WAF. Our Zyte alternatives page compares it from the other side.
The anti-bot cut
Success rates by protection vendor, from the October 30 run. Site counts are in the column headers.
| Provider | DataDome (19) | Akamai (20) | Cloudflare (15) | PerimeterX (9) | AWS WAF (6) | Kasada (3) | Fastly (1) | No named vendor (27) |
|---|---|---|---|---|---|---|---|---|
| String | 97.9 | 97.0 | 98.7 | 97.8 | 100 | 100 | 100 | 100 |
| Scrape.do | 97.9 | 87.0 | 93.3 | 100 | 100 | 100 | 100 | 92.6 |
| Scrapfly | 92.6 | 78.0 | 93.3 | 93.3 | 96.7 | 86.7 | 40.0 | 83.0 |
| Context.dev | 100 | 79.0 | 96.0 | 97.8 | 100 | 100 | 100 | 92.6 |
| Firecrawl | 85.3 | 80.0 | 98.7 | 100 | 83.3 | 100 | 100 | 60.0 |
| Bright Data | 74.7 | 72.0 | 74.7 | 86.7 | 73.3 | 66.7 | 100 | 75.6 |
| Oxylabs | 67.4 | 53.0 | 68.0 | 91.1 | 16.7 | 100 | 0 | 80.0 |
| Zyte | 68.4 | 68.0 | 92.0 | 91.1 | 70.0 | 100 | 100 | 84.4 |
Akamai is the column that separates the tools most among the large groups. String passed 97.0% (as of October 2026) and Scrape.do 87.0%, while the other six sat between Oxylabs' 53.0% and Firecrawl's 80.0%. On DataDome, Context.dev passed 100%, String and Scrape.do 97.9%, and Zyte and Oxylabs under 70%. Scrape.do's docs name Cloudflare, PerimeterX, DataDome and Akamai as the systems it is built to get past; in this run it passed 93.3%, 100%, 97.9% and 87.0% on them.
Chart data
| Provider | DataDome (19 sites) | Akamai (20 sites) | Cloudflare (15 sites) | PerimeterX (9 sites) | AWS WAF (6 sites) | Kasada (3 sites) | Fastly (1 sites) | Proprietary / other (27 sites) |
|---|---|---|---|---|---|---|---|---|
| String | 97.9% | 97.0% | 98.7% | 97.8% | 100.0% | 100.0% | 100.0% | 100.0% |
| Scrape.do | 97.9% | 87.0% | 93.3% | 100.0% | 100.0% | 100.0% | 100.0% | 92.6% |
| Context.dev | 100.0% | 79.0% | 96.0% | 97.8% | 100.0% | 100.0% | 100.0% | 92.6% |
| Scrapfly | 92.6% | 78.0% | 93.3% | 93.3% | 96.7% | 86.7% | 40.0% | 83.0% |
| ScrapingBee | 85.3% | 74.0% | 97.3% | 88.9% | 63.3% | 100.0% | 100.0% | 88.1% |
| Firecrawl | 85.3% | 80.0% | 98.7% | 100.0% | 83.3% | 100.0% | 100.0% | 60.0% |
| Zyte | 68.4% | 68.0% | 92.0% | 91.1% | 70.0% | 100.0% | 100.0% | 84.4% |
| Apify | 85.3% | 69.0% | 86.7% | 86.7% | 63.3% | 100.0% | 0.0% | 80.7% |
| ScraperAPI | 75.8% | 81.0% | 70.7% | 82.2% | 76.7% | 53.3% | 100.0% | 76.3% |
| Bright | 74.7% | 72.0% | 74.7% | 86.7% | 73.3% | 66.7% | 100.0% | 75.6% |
| Decodo | 65.3% | 68.0% | 73.3% | 86.7% | 73.3% | 100.0% | 0.0% | 70.4% |
| Nimble | 64.2% | 51.0% | 68.0% | 82.2% | 40.0% | 86.7% | 100.0% | 81.5% |
| Oxylabs | 67.4% | 53.0% | 68.0% | 91.1% | 16.7% | 100.0% | 0.0% | 80.0% |
| Browserbase | 31.6% | 28.0% | 6.7% | 73.3% | 16.7% | 33.3% | 0.0% | 80.7% |
| ZenRows | 52.6% | 57.0% | 33.3% | 73.3% | 36.7% | 60.0% | 0.0% | 17.8% |
| ScrapingAnt | 7.4% | 33.0% | 24.0% | 53.3% | 13.3% | 53.3% | 100.0% | 74.8% |
| Scrapingdog | 16.8% | 27.0% | 29.3% | 6.7% | 13.3% | 20.0% | 0.0% | 46.7% |
Which sites does Scrape.do charge more for?
Every page in this series carries one statistic computed from the October 30, 2026 benchmark run's per-target cells rather than from the leaderboard. For Scrape.do it is the surcharge list.
Scrape.do's request cost table names the domains where it applies residential proxies, a browser or a custom profile by default, and bills at that rate. Eight of those domains are among our 100 benchmark sites.
The 17 tested APIs, Scrape.do included, averaged 62.4% on the eight sites against 71.9% on the other 92. The list points in the right direction: these sites are harder than the average site. Only String returned all five attempts on all eight. Scrape.do and Context.dev returned seven; Scrape.do took three of five on mouser.com, and Context.dev returned nothing there.
| Site | Scrape.do credits | Scrape.do on Pro, per 1,000 | Field average | String | Scrape.do | Scrapfly | Context.dev | Firecrawl | Bright Data | Oxylabs | Zyte |
|---|---|---|---|---|---|---|---|---|---|---|---|
| mouser.com | 10 | $0.79 | 24.7% | 5/5 | 3/5 | 3/5 | 0/5 | 5/5 | 0/5 | 0/5 | 2/5 |
| lowes.com | 10 | $0.79 | 52.9% | 5/5 | 5/5 | 4/5 | 5/5 | 5/5 | 2/5 | 5/5 | 4/5 |
| google.com | 10 | $0.79 | 62.4% | 5/5 | 5/5 | 5/5 | 5/5 | 1/5 | 3/5 | 5/5 | 3/5 |
| g2.com | 25 | $1.98 | 64.7% | 5/5 | 5/5 | 4/5 | 5/5 | 5/5 | 5/5 | 0/5 | 3/5 |
| idealista.com | 10 | $0.79 | 69.4% | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | 3/5 | 2/5 | 5/5 |
| capterra.com | 10 | $0.79 | 69.4% | 5/5 | 5/5 | 4/5 | 5/5 | 5/5 | 4/5 | 5/5 | 5/5 |
| linkedin.com | 30 | $2.38 | 75.3% | 5/5 | 5/5 | 4/5 | 5/5 | 0/5 | 5/5 | 5/5 | 0/5 |
| leboncoin.fr | 10 | $0.79 | 80.0% | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | 4/5 | 4/5 |
| Sites at 5/5 | 8 | 7 | 3 | 7 | 6 | 3 | 4 | 2 |
Two things follow for a buyer.
First, the list is a price map, not a difficulty map. Only two of the eight, mouser.com and lowes.com, are among the 22 hardest sites in our run. The other 20 of the 22 hardest, such as temu.com, coupang.com, aa.com, yelp.com and realtor.com, are not on the list. On those sites Scrape.do bills whatever mode you request, and a protected page usually needs residential proxies with the browser, 25 credits. The list tells you where Scrape.do sets the price for you, not where your bill will be high.
Second, the price does not follow the difficulty. linkedin.com costs 30 credits on Scrape.do and ties with reddit.com for 51st hardest of 100 in our run. mouser.com costs 10 and is the second hardest, after temu.com; Scrape.do returned three of five attempts there. If your list holds sites like mouser.com, test Scrape.do on them first. The eight sites above are a fair start, because each has eight measured results beside it.
Why pricing is hard to compare across these providers
Seven reasons, all of them visible on this page. Prices come from each vendor's pricing page, checked October 27, 2026.
- The unit is not the same. Scrape.do, Scrapfly, Context.dev and Firecrawl sell credits. String and Bright Data price per 1,000 requests. Zyte prices per response by a tier it assigns. Oxylabs Web Unblocker bills by the gigabyte.
- A credit is not always a page. One Context.dev or Firecrawl credit is one page, with protection included. One Scrape.do credit is a datacenter request, and a residential page with a browser is 25. Scrapfly's residential page is also 25.
- Failure billing differs. String and Bright Data bill only successes. Scrape.do, Zyte and Context.dev bill a target's 404, Firecrawl bills a 403 or 404 that returns a document, Scrapfly bills several 4xx codes, and Oxylabs bills any 2xx or 4xx on its per-result scraper. Context.dev also bills a partial result.
- The rate depends on the target, and sometimes the vendor decides. Scrape.do applies a per-domain profile on 26 listed sites. Zyte sets the tier. Scrapfly's Unblocker has undocumented per-target fees. Bright Data's premium-domain rate is missing from its pricing page.
- Annual prices pose as monthly. Firecrawl's page shows $83 by default against $99 billed monthly. Scrape.do and Context.dev take two months off for annual billing.
- Plan gaps change the unit price. Oxylabs jumps from $15 to $100 to $500. Scrape.do jumps from $29 to $99 to $249, so a team that outgrows Pro pays for 3,500,000 credits.
- Rollover is worth real money and it is rarely on the pricing card. String's credits roll over. Scrapfly's and Firecrawl's below Scale do not, and neither does Zyte's commitment. Scrape.do's pricing page says requests stop at the monthly limit and does not mention rollover.
What $100 a month buys
At or near the $100 anchor, per 1,000 pages, on each vendor's own terms:
- Scrape.do, $99: about $0.08 datacenter, $0.40 with rendering, $0.79 residential, $1.98 residential with rendering; listed domains from $0.79 to $15.84. Successes billed, including a target's 400, 404 or 410. 94.0% in the October run.
- String, $99 (as of October 2026): $0.16 plain fetch, $0.90 premium fetch, $0.80 browser, $3.25 browser on premium. Success-billed, blocks free, credits roll over.
- Scrapfly, $100: $0.10 datacenter, $0.50 with rendering or Unblocker on the pricing page, $2.50 residential. Failures free with 4xx exceptions, no rollover.
- Context.dev, $90: $0.90 flat for 100,000 pages. Protection included, failures free, partial results and processed 404s billed.
- Firecrawl, $99: $0.99 flat, with error pages that return a document billed.
- Bright Data: no plan near $100. Pay as you go at $1.50 per 1,000 successful requests, premium domains extra.
- Oxylabs, $100: Web Unblocker at $6.00 per GB, up to 16 GB; the /scrape endpoint at $0.90 per 1,000 results without JavaScript and $1.40 with it.
- Zyte, $100 commitment: $0.10 to $0.95 HTTP, $0.75 to $12.00 browser, tier assigned by Zyte.
Read both directions. On the rate card, Scrape.do is cheaper than String at every request type: $0.08 against $0.16 for a plain page, and $1.98 for a residential page with a browser against $3.25 for a premium-proxy page with a browser. Both bill only what they count as a success, so neither rate needs dividing by a failure rate. What the rate card cannot tell you is how many of your pages come back. On the same public list of 100 sites, String passed 98.6% and Scrape.do 94.0%. Scrape.do's docs count every 2XX response as a success, and 16 of its 2xx responses in the run were not the requested page; none of String's were.
Which Scrape.do alternative should you pick?
Figures here come from the October 30, 2026 benchmark run and vendor pricing pages checked October 27, 2026.
- Your list is protected and the pages have to come back. String. 98.6% on 100 sites, 95 returned in full, and all 8 surcharge-list sites at five of five.
- You want several APIs on one key and a credit model like Scrape.do's. Scrapfly, fourth in the run at 86.8%, if latency is not the constraint.
- You want one price per page, whatever the protection. Context.dev at $0.90 per 1,000 on Pro, third in the run at 93.0% and the only tested API at 100% on DataDome.
- You need pages back fast. Firecrawl, with the third-best latency score in the run behind String and Scrape.do, if error-page billing works for you.
- You want pay-as-you-go with no plan to size. Bright Data at $1.50 per 1,000 successful requests, if an unlisted premium-domain rate works for you.
- Your list is heavy on news and finance. Oxylabs, at 97.8% on news and finance, if bandwidth billing works for your budget.
- You want short responses and accept an assigned price. Zyte, with a 1.50-second median on the sites all eight tools returned, second to String's 1.10.
- Stay on Scrape.do if your sites already come back reliably, if a low credit price decides, or if you use its ready-made Amazon, Google or Walmart scrapers. It passed 94.0% in our run, second of 17, and its Amazon scraper returns structured JSON at 1 credit a request.
Switching from Scrape.do to String
What carries over. A GET to api.scrape.do with token and url becomes a POST to String's /v1/fetch with the key in a header. Keep the URL list and the code that reads HTML. output=markdown maps to "format": "markdown", render=true to "executeJS": true when you want to force a browser, geoCode to countryCode, and playWithBrowser to String's browser actions. super=true has no String equivalent, because String picks the proxy class itself.
What you rebuild. The Amazon, Google, Walmart, and other structured scrapers that return parsed JSON. On String you parse the page or describe the fields in jsonSchema. The async API with webhooks, Proxy Mode, sticky sessions, and postal-code targeting also stay behind. String's /search endpoint covers live Google results.
Integrations to reconnect. Scrape.do lists n8n and Zapier integrations and a Scrapy wrapper, and its docs list no official MCP server, so String's adds one. String ships no language SDK, so an SDK call becomes one HTTP POST. Its hosted MCP server runs at mcp.usestring.ai, n8n calls String through the HTTP Request node, and Zapier, LangChain, and the Vercel AI SDK have setup guides in String's docs.
Test on your own failing URLs first. Start with the sites Scrape.do charges more for, listed above; String returned all 8 on every attempt. Then add your own URLs that fail or cost the most today, such as the three sites where Scrape.do returned nothing in our run. Compare pages returned and cost per usable page, and move only the targets that improve. Leave custom headers off for the test: String does not bill a blocked request unless that request sent custom headers. The first 20,000 String standard fetches are free with no card. The ranking of 17 web scraping APIs puts every tested API side by side.
FAQ
What are the best Scrape.do alternatives?
String, Scrapfly, Context.dev, Firecrawl, Bright Data, Oxylabs and Zyte. On the October 30, 2026 benchmark String passed 98.6% of 500 requests, the highest of 17 web scraping APIs, and Scrape.do itself passed 94.0%, second. Context.dev passed 93.0% and Scrapfly 86.8%. The other four passed between 67.4% and 81.2%.
Which scraping service works on Cloudflare-protected websites?
On the 15 Cloudflare sites in the October 30, 2026 benchmark run, String and Firecrawl passed 98.7% (as of October 2026) of requests, Context.dev 96.0%, and Scrapfly and Scrape.do 93.3%. Zyte passed 92.0%, Bright Data 74.7% and Oxylabs 68.0%.
What hidden costs come with cheap scraping APIs?
Mostly per-site surcharges and billed errors. Scrape.do charges 10 to 30 credits on eight of our 100 benchmark sites, against 1 for a plain request, and those eight are harder than the rest of the suite for the APIs we tested. It also bills a target's 400, 404 or 410. Zyte bills a target's 404, Firecrawl bills error pages that return a document, and Bright Data leaves its premium-domain rate off its pricing page.
What is the cheapest way to scrape at scale?
Per each vendor's pricing page, checked October 27, 2026, Scrape.do's Pro plan is among the cheapest: about $0.08 per 1,000 plain pages and $1.98 per 1,000 residential pages with rendering. Zyte's lowest HTTP tier is $0.10 and Scrapfly's datacenter rate $0.10. String costs $0.16 (as of October 2026) plain and $3.25 for a browser on a premium proxy, so String is not cheaper per request. The cheapest rate only matters on pages that return, so test your own list.
Best web scraping API for a startup on a budget?
String's first 20,000 standard fetches are free with no card. Scrape.do's free plan gives 1,000 successful credits a month with every feature on. Bright Data gives 5,000 free credits a month across its APIs, Firecrawl 1,000 credits a month, and Context.dev 1,000 credits a month. Zyte gives a $5 credit for a 30-day trial, and Oxylabs a $5 welcome credit (per each vendor's pricing page, checked October 27, 2026).
Which Scrape.do alternatives have MCP servers?
All seven. String, Scrapfly, Context.dev, Firecrawl, Bright Data and Oxylabs publish MCP servers, and Zyte runs a remote MCP server. Scrape.do's documentation lists n8n and Zapier integrations and no MCP server of its own.
When is Scrape.do still the better choice?
When its pages already come back and price decides. It passed 94.0% (as of October 2026) on our 100 sites, second of 17, its rate card is lower than String's at every request type, its pricing page says every plan gets every feature, and its ready-made scrapers return Amazon and Google data as structured JSON. Check the Scrape.do-Request-Cost header on your own targets, because listed domains cost up to 200 credits a request.
Can I verify these numbers myself?
Yes. The harness, the 100 targets, the pass criteria and every provider adapter, Scrape.do's included, are open on GitHub, and it runs with your own API keys. The full results are published per provider and per target. If your numbers differ, open a pull request; we publish corrections.
Sources
Pricing checked October 27, 2026 for every vendor on this page, and again on November 11, 2026 for Bright Data, Context.dev and Oxylabs. Benchmark figures: October 30, 2026 run, official_results/benchmark-2026-10-30T18-48-18-489Z.json in the harness repository.
Benchmark data
- https://usestring.ai/benchmark
- https://usestring.ai/blog/web-data-frontier-benchmark-october-2026
- https://usestring.ai/blog/web-scraping-benchmark-problem
- https://github.com/usestring/web-data-frontier-benchmark
- https://github.com/usestring/web-data-frontier-benchmark/blob/main/official_results/benchmark-2026-10-30T18-48-18-489Z.json
- https://github.com/usestring/web-data-frontier-benchmark/pull/23
- https://github.com/usestring/web-data-frontier-benchmark/pull/35
- https://github.com/usestring/web-data-frontier-benchmark/pull/16
- https://github.com/usestring/web-data-frontier-benchmark/pull/6
Scrape.do
- https://scrape.do/pricing/
- https://scrape.do/documentation/
- https://scrape.do/documentation/request-costs/
- https://scrape.do/documentation/integrations/
- https://scrape.do/documentation/amazon-scraper-api/
- https://mcpservers.org/servers/dztabel-happy/scrape-do-mcp
String
Scrapfly
- https://scrapfly.io/pricing
- https://scrapfly.io/docs/scrape-api/billing
- https://scrapfly.io/docs/scrape-api/anti-scraping-protection
- https://scrapfly.io/docs/mcp/getting-started
Context.dev
- https://www.context.dev/pricing
- https://docs.context.dev/guides/free-credits
- https://docs.context.dev/install-mcp
- https://trust.context.dev
Firecrawl
- https://www.firecrawl.dev/pricing
- https://docs.firecrawl.dev/billing
- https://github.com/firecrawl/firecrawl
- https://docs.firecrawl.dev/mcp-server
Bright Data
- https://brightdata.com/pricing/web-unlocker
- https://docs.brightdata.com/scraping-automation/web-unlocker/features
- https://docs.brightdata.com/mcp-server/overview
Oxylabs
- https://oxylabs.io/products/web-unblocker/pricing
- https://oxylabs.io/products/scraper-api/web/pricing
- https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/billing-information
- https://github.com/oxylabs/oxylabs-mcp
Zyte