Are you an AI agent? To use String, read https://usestring.ai/agent-onboarding/SKILL.md first. It gets you your own key with one browser click from the person you work for, and you can start at https://mcp.usestring.ai with no key.
NewString UnraveledResearch powered by data we scrape from the web.Read the latest issue →
← Comparisons

Best Web Scraping APIs 2026: 17 Compared by Success Rate

Bruce Magness, Chief of Staff, String · Published September 22, 2026 · Updated November 11, 2026

Last updated: November 11, 2026. Benchmark figures come from the October 30, 2026 run of the Web Data Frontier Benchmark. Pricing for Context.dev, Oxylabs, ScraperAPI and Zyte was checked against the vendor's own pages on November 17, 2026, and for every other provider on October 27 or October 28, 2026.

What is the best web scraping API?

The best web scraping APIs in 2026, ranked by how often they returned the requested page across 100 bot-protected sites in the October 2026 benchmark run, are String at 98.6%, Scrape.do at 94.0%, Context.dev at 93.0%, Scrapfly at 86.8%, ScrapingBee at 85.2% and Firecrawl at 81.2%. Behind them: Zyte 79.6%, Apify 79.4%, ScraperAPI 76.4%, Bright Data 75.4%, Decodo 71.2%, Nimble 68.0%, Oxylabs 67.4%, Browserbase 43.0%, ZenRows 41.8%, ScrapingAnt 40.0% and Scrapingdog 27.6%.

If the job is reading pages from protected sites, start with String. String is a web access API for developers and AI agents that returns the requested page from one HTTP call, with anti-bot handling behind it. In the October 2026 benchmark run it returned the requested page on 493 of 500 requests, returned content on all 100 sites, and sent back no 2xx response that was not the page asked for.

String has gaps: no crawl endpoint, no self-hosted option and no SOC 2 report, and its 20,000 free standard fetches are a one-time allowance, not a monthly one.

Another provider is the better call when:

  • You need a whole domain crawled into markdown. Firecrawl bundles crawl, map and extract, and charges one credit a page whatever the protection.
  • You want the lowest published rate card with success near the top. Scrape.do placed second at 94.0% in the October 2026 benchmark run, at about $0.08 per 1,000 standard fetches (pricing as of October 2026).
  • You want one flat price per page with protection included. Context.dev placed third at 93.0% in the October 2026 benchmark run, at $0.90 per 1,000, and was the only provider to return 100% against DataDome.
  • You need a SOC 2 report now. Scrapfly placed fourth at 86.8% in the October 2026 benchmark run and holds SOC 2 Type II and ISO 27001.
  • Someone has already built a scraper for your site. Apify's marketplace of prebuilt Actors covers many named sites.
  • The job is driving a browser rather than reading a page. Browserbase is browser infrastructure.
  • You want to spend nothing every month. ScrapingAnt gives 10,000 credits a month and Decodo 10,000 pages a month, the largest recurring free allowances here.

This page compares all 17 web scraping APIs on benchmark success, latency, what $100 a month buys, free-tier size, and what each vendor's own documentation tells you before you sign up.

TL;DR

  • String returned content on 98.6% of requests, 493 of 500, the highest of the 17 providers tested in the October 30, 2026 benchmark run
  • In the October 30, 2026 benchmark run, the gap between first and last is 71.0 points. Scrapingdog, the lowest, returned 138 of 500
  • The other 16 providers sent back 400 responses with a 2xx status that were not the requested page. String sent back none, which matters most when the pages feed a training set or a retrieval index
  • In the October 30, 2026 benchmark run, no site was returned on all five attempts by all seventeen providers, and none shut out all seventeen. On 95 of the 100, at least one provider returned the page every time and at least one returned nothing at all. String returned 90 of those 95 on every attempt and none of them came back empty
  • Twelve of the seventeen bill a target's own 404 page, String included. Three also bill a 403 block: Firecrawl charges a credit on a 403 or a 404, Oxylabs counts every 4xx response as successful, and Decodo bills a 403 that is not empty
  • Of the sixteen free tiers listed below, ten refresh every month. ScrapingAnt gives 10,000 credits a month with no card, tied with Decodo's 10,000 pages for the largest. String gives 20,000 standard fetches once, with no card
  • At the plan nearest $100 a month, the configuration each vendor ran on the benchmark costs from $0.90 per 1,000 (String and Context.dev) to $4.95 (ZenRows) where the rate is fixed, and up to $7.43 where it depends on the target. Decodo's premium proxies without JavaScript cost less, at $0.70
  • Every result comes from a public harness you can rerun with your own API keys

At a glance

Provider Best for Benchmark success Latency score What $100 a month buys The catch
String Protected pages that must return every time 98.6% (493/500) 4.24s Growth $99/mo, all of it usage at $0.16 per 1,000 plain fetches or $0.90 premium; blocked requests free, a site's 404 bills No crawl endpoint, no self-hosting, no SOC 2 report
Scrape.do A low published rate card on a simple GET endpoint 94.0% (470/500) 5.08s Pro $99/mo, 1,250,000 credits: about $0.08 datacenter, $1.98 residential with a browser A target's 404 is billed, and listed domains carry their own price
Context.dev One flat credit per page, protection included 93.0% (465/500) 10.96s Pro $90/mo buys 100,000 credits at 1 credit a page, $0.90 per 1,000 A target's 404 is billed; returned nothing on 6 of the 100 sites
Scrapfly Several APIs on one key 86.8% (434/500) 19.62s Pro $100/mo, 1,000,000 credits; $0.10 to $2.50 per 1,000 by proxy pool ASP can escalate the proxy pool at a rate it does not publish
ScrapingBee Auto-Mode escalation that bills the winner only 85.2% (426/500) 20.30s Startup $99/mo, 1,000,000 credits: $0.099 standard, $2.475 premium with JavaScript Its own docs route e-commerce to the 25-credit tier; prices exclude VAT
Firecrawl Crawling a whole domain to markdown 81.2% (406/500) 8.87s Standard $99/mo billed monthly, 100,000 pages at 1 credit each, easy or protected Charged on a target 403 or 404
Zyte Letting the vendor price each site by difficulty 79.6% (398/500) 14.43s $100 commitment: $0.10 to $0.95 per 1,000 HTTP responses, $0.75 to $12.00 browser Zyte assigns your tier and you cannot see it without an account
Apify A prebuilt scraper for a named site 79.4% (397/500) 24.87s No $100 plan. The plan fee is spendable usage, so $100 buys about 66,700 Web Fetch calls at the Starter rate of $1.50 per 1,000 Unused prepaid usage expires monthly
ScraperAPI Per-request cost caps 76.4% (382/500) 15.19s No $100 plan. Startup $149 buys 1,000,000 credits and Hobby $49 buys 100,000; a bypassed page costs 11 Anti-bot bypass adds 10 credits, so the headline rate is not the real rate
Bright Data Proxy scale and enterprise compliance 75.4% (377/500) 27.88s No $100 plan. Pay as you go is $1.50 per 1,000 requests Premium domains cost more at an unpublished rate
Decodo A published rate for every configuration 71.2% (356/500) 28.29s $99/mo: $0.30 standard, $0.70 premium proxies, $1.10 premium with JavaScript Prices exclude VAT; 48 of its 2xx responses were not the requested page
Nimble Search and extract behind one usage meter 68.0% (340/500) 22.65s Usage priced: about 100,000 Extract requests at $1.00 per 1,000 Named plans start at $2,500 a month billed annually
Oxylabs Bandwidth billing and a broad product line 67.4% (337/500) 16.62s Basic $100/mo: Web Unblocker at $6.00/GB, about 16 GB Billed on bandwidth, so there is no per-page figure
Browserbase Driving a browser, not reading a page 43.0% (215/500) 18.01s Startup $99/mo: 500 browser hours, 10,000 Fetch calls, then $4 per 1,000 with proxies Advanced Stealth is Scale-plan only, not on any self-serve tier
ZenRows An MCP server on every plan, free included 41.8% (209/500) 21.91s Launch L2 $99/mo, 500,000 credits: $0.20 standard, $4.95 protected The pricing page shows the annual-equivalent price by default
ScrapingAnt A monthly free tier of 10,000 credits 40.0% (200/500) 18.39s No $100 plan. Startup $49 buys 500,000 credits; a protected page costs 125 125 credits for browser plus residential is $12.25 per 1,000
Scrapingdog A cheap published standard fetch 27.6% (138/500) 31.52s Standard $90/mo, 1,000,000 credits: $0.09 standard, $2.25 with JavaScript and premium proxy 6.7% against PerimeterX, the lowest of the seventeen, and the slowest latency score

The latency score is a per-target p75 of successful attempts. A provider that returns nothing on a target inherits the p75 of the providers that did succeed there, and a target nobody clears scores the 90-second timeout. It refuses to reward fast failures.

How we tested these web scraping APIs

The benchmark sends the same 100 URLs to 17 providers, five times each: 8,500 live, billable requests.

A request passes only when the response contains a marker from the real page: a product title, an article headline, or another known piece of content. A captcha page returning HTTP 200 fails. A blank response fails. A fast 403 fails. The benchmark measures whether the requested content actually came back.

Most targets are protected retail, travel, news and social sites. That is deliberate. Easy pages tell you whether an HTTP client works. Hard pages tell you whether a web-access product works.

Each provider runs through its own documented anti-bot configuration, one general adapter per provider, using the settings that vendor's own troubleshooting docs prescribe for a blocked page. Several vendors also sell a dedicated endpoint for a specific site, and a dedicated endpoint would plausibly return a page the general path did not. The per-provider sections say so where it applies. If you run your own scraper instead of an API, we published the scripts we ran for bypassing Cloudflare when scraping and the nine techniques in how to scrape a website without getting blocked.

The September 16, 2026 benchmark run was the first in which every provider ran at its strongest published setting, and several had been running below theirs. Two moved a long way for that reason between August and September: ScraperAPI from 64.2% to 84.0% and ScrapingBee from 29.7% to 73.0%. Those jumps measured our adapters catching up more than a product change. The October 30 run keeps those settings and runs the same 100 sites, with six site fixtures repaired. Scrape.do is new to the field this run, so it has no September number to compare.

We built the public harness, and String ranks first in it. Do not take our word for it. The targets, the pass rule, the provider adapters and the raw results are public, and the repo runs with your own API keys. How to evaluate a web scraping API shows how to run the same test on your own URLs, and how many you need.

Chart data
ProviderSuccess ratePassedLatency score
String98.6%493/5004.24s
Scrape.do94.0%470/5005.08s
Context.dev93.0%465/50010.96s
Scrapfly86.8%434/50019.62s
ScrapingBee85.2%426/50020.30s
Firecrawl81.2%406/5008.87s
Zyte79.6%398/50014.43s
Apify79.4%397/50024.87s
ScraperAPI76.4%382/50015.19s
Bright75.4%377/50027.88s
Decodo71.2%356/50028.29s
Nimble68.0%340/50022.65s
Oxylabs67.4%337/50016.62s
Browserbase43.0%215/50018.01s
ZenRows41.8%209/50021.91s
ScrapingAnt40.0%200/50018.39s
Scrapingdog27.6%138/50031.52s
Overall success rate across all 500 requests per provider. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

The vendor decides the outcome on 95 of the 100 pages

Every provider in this run was sent the same list. No site came back on all five attempts for all seventeen providers, and no site came back for none of them. temu.com, which shut out every provider in September, went to String alone on all five attempts after its fixture was repaired. databricks.com came closest to a clean sweep again: Scrapingdog returned it twice out of five and every other provider returned it every time.

In the October 30, 2026 benchmark run, on 95 of the 100, at least one provider returned the page on all five attempts while at least one other returned nothing at all across five attempts. The other five, expedia.com, ashleyfurniture.com, verizon.com, walmart.com and databricks.com, had at least one clean pass and no total shutout.

So on 95% of the hard target list in the benchmark, the choice of vendor is the difference between having the page and not having it. Not slower, not costlier: absent.

The spread inside that decision set is wide. In the October 30, 2026 benchmark run, String returned 90 of the 95 on all five attempts and returned nothing on none. Scrape.do and Context.dev both cleared 86, with 3 and 6 shutouts. Firecrawl cleared 75 and was shut out on 17. Scrapfly cleared 65 with 5 shutouts. At the other end, ZenRows cleared 28 and returned nothing on 53 of the 95, Browserbase cleared 32 with 53 shutouts, and Scrapingdog cleared 9 and returned nothing on 47.

This is why an average success rate hides the decision. A provider that succeeds on seven requests in ten is not a provider that returns every page a little worse. It is a provider that returns most of your list perfectly and hands you nothing at all on the rest, and the sites in that second group are usually the ones the project was built for.

Best web scraping API for AI and machine learning data collection

For AI and machine learning data collection, String returned 493 of 500 protected pages in the October 2026 benchmark run and was the only one of the 17 to send back zero wrong pages with a 2xx status.

A training set or a retrieval index fails in a way a one-off scrape does not. A blocked request that comes back as HTTP 200 with a challenge page, a cookie wall or an empty shell gets stored as if it were the page. Nobody reads it, so it goes into the corpus and gets chunked, embedded or trained on.

Four things decide whether an API is fit for that job:

  • Coverage comes first, because pages that never come back are missing from the dataset and the gaps skew it toward sites that are easy to fetch. Success in the October 2026 benchmark run runs from 98.6% to 27.6%.
  • Every 2xx response that is not the requested page has to be caught before it reaches the pipeline. The table below counts them for each provider.
  • The output should be markdown or structured JSON, not raw HTML. String returns markdown when the request sets "format": "markdown", and which scraping API returns clean structured JSON covers the JSON side.
  • An agent needs a way to call the API. String, Scrapfly, ZenRows, ScrapingAnt and Bright Data each offer an MCP server, per the vendor sections below.

How many 2xx responses were not the requested page

The 16 providers other than String sent back 400 responses with a 2xx status that did not contain the requested page, out of 8,000 requests.

The last column is the share a status-code check would let through: wrong pages divided by everything that check would keep, meaning the pages returned plus the wrong pages. It counts every response that passed the content check as one the status check keeps.

Provider Pages returned (of 500) 2xx, not the page Share a status-code check lets through
String 493 0 0.0%
Context.dev 465 5 1.1%
Bright Data 377 6 1.6%
Zyte 398 8 2.0%
Scrape.do 470 16 3.3%
Firecrawl 406 15 3.6%
Oxylabs 337 14 4.0%
ZenRows 209 10 4.6%
ScraperAPI 382 23 5.7%
Apify 397 28 6.6%
Scrapfly 434 35 7.5%
ScrapingBee 426 41 8.8%
Nimble 340 33 8.8%
Browserbase 215 26 10.8%
Scrapingdog 138 17 11.0%
Decodo 356 48 11.9%
ScrapingAnt 200 75 27.3%

In the October 2026 benchmark run, ScrapingAnt's 75 wrong pages are 27.3% of everything it returned with a 2xx status. More than one row in four that a status-code filter keeps would be a wall, not a page. Decodo, Scrapingdog and Browserbase are each above 10%. Context.dev let 1.1% through. Bright Data, tenth on success, let 1.6% through, so success rate and a clean dataset are separate questions.

Whatever you pick, check content, not status codes. The benchmark passes a response only when it contains a known marker from the real page, and a pipeline can run the same test. How to detect a bot block that returns HTTP 200 and how to validate scraped data quality show the checks.

To test it on your own corpus, send a sample of your URL list through /v1/fetch with "format": "markdown". The first 20,000 standard fetches are free with no card. If the model needs search results rather than pages, web search API vs web scraping API explains which one an LLM app needs.

Starting for free: what each tier actually gives you

Ten of the sixteen allowances below refresh every month. The rest give a one-time grant or a trial window, which is enough to test a target list and not enough to run anything. Scrape.do has a free plan, but its size was not part of this page's pricing check, so it is not in the table.

Provider Free allowance Refreshes monthly Card required
String 20,000 standard fetches No, one time No
ScrapingAnt 10,000 credits Yes No
Decodo 10,000 pages on the free plan Yes Not stated
Nimble 5,000 requests Yes No
ZenRows 5,000 credits Yes No
Bright Data 5,000 requests Yes No
Apify $5 of platform usage Yes No
Firecrawl 1,000 credits Yes No
Context.dev 1,000 credits Yes No
Scrapfly 1,000 credits No, no time limit No
ScrapingBee 1,000 credits No, one time No
ScraperAPI 1,000 credits, or 5,000 on a 7-day trial Yes, the free credits; the trial is one time No
Browserbase 1 browser hour, 1,000 Fetch calls Yes No
Scrapingdog 100 credits No No
Zyte $5 of credit in the first billing month No Not stated
Oxylabs $5 welcome credit No, one time Not stated

A credit is not a page. On ScrapingAnt, the free 10,000 credits buy 10,000 plain fetches, 1,000 browser-rendered pages, or 80 pages through a browser on a residential proxy, because those three configurations cost 1, 10 and 125 credits. Read the vendor's credit table before you read its free-tier number.

What the docs tell you before you sign up

Three things decide whether a first week goes well: whether the vendor publishes what each configuration costs, whether it says who pays when a page is blocked, and whether you can price your own target list without an account.

Provider Publishes a per-configuration credit table States the failure-billing rule Can price your own URL without an account
ZenRows Yes, in the docs Yes Yes, weights are fixed on every plan
ScrapingAnt Yes Yes Yes
Scrapingdog Yes, on the pricing page Yes Yes
ScrapingBee Yes Yes, per status code Yes
Decodo Yes, four rates per plan Yes Yes
Scrapfly Yes Yes, with a 30% fairness cap No, ASP escalation is unpublished
Scrape.do Yes, with per-domain prices Yes, by status code Yes, listed domains are priced in the docs
String Yes, four paths per plan Yes Yes
Firecrawl One flat credit, so no table needed Yes Yes
Context.dev One flat credit, so no table needed Yes Yes
Apify Per Actor, not per configuration Yes, per event Yes, each Actor's page states its own price
ScraperAPI Yes Yes No, the Domain Cost Estimator is in the dashboard
Zyte Yes, five tiers Yes No, the per-site lookup needs an account
Bright Data Partly, premium domains are unpublished Yes No
Oxylabs No, billed on bandwidth Yes No, no per-page unit exists
Browserbase Yes, per API Not stated for blocked pages Yes
Nimble Per API, not per configuration Not stated Partly

Two of these vendors contradict themselves on their own pages, and both contradictions cost money. Scrapingdog's pricing page says "no surprise multipliers at the end of the month" a few hundred pixels above a table charging 25 credits for a rendered page on a premium proxy. ScrapingAnt's homepage FAQ says most requests cost between 1 and 25 credits, while the docs table tops out at 125. In both cases the more specific page is the one that bills you.

String: 98.6%, and no charge when a page is blocked

Pricing. Growth is $99 a month (as of October 2026) and includes $99 of usage at $0.16 per 1,000 plain fetches, $0.90 premium, $0.80 with a browser, $3.25 with both, per the pricing page. Starter is $19. Blocked requests are free, a site's own 404 bills, and unused credits roll over. The first 20,000 standard fetches are free with no card.

Benchmark success. 98.6%, 493 of 500, first of seventeen. 95 of the 100 sites returned on all five attempts, and every one of the 100 returned at least once.

Latency. 4.24s, the fastest in the run, ahead of Scrape.do's 5.08s.

Strengths. The highest measured success on protected pages, the fastest latency score, no 2xx response in the run that was not the requested page, four published rates with no credit conversion, and a hosted MCP server on the public registry. It led or tied the lead in every anti-bot column of the October 2026 benchmark except DataDome, where Context.dev returned 100% against String's 97.9%, and PerimeterX, where Scrape.do and Firecrawl returned 100% against 97.8%.

Weaknesses. No crawl endpoint and no self-hosted option. String has no SOC 2 report. Its Enterprise rate card is not published, so the high-volume price cannot be verified from a public page. It returned kroger.com on two of five attempts, and yellowpages.com, marketwatch.com, barrons.com and skyscanner.net on four.

You can run your own list against it:

curl https://request.usestring.ai/v1/fetch \
  -H "Authorization: Bearer $STRING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.zillow.com", "format": "markdown"}'

Scrape.do: second on success, new to this run

Pricing. As of October 2026, Pro is $99 a month for 1,250,000 credits, about $0.08 per 1,000 credits. A plain datacenter request is 1 credit, the headless browser 5, a residential or mobile request 10, and residential with the browser 25: about $0.08, $0.40, $0.79 and $1.98 per 1,000 pages. On the domains its request cost docs list, it applies its own profile and price. The same docs count 2XX, 400, 404 and 410 as successful, so a target's 404 bills.

Benchmark success. 94.0%, 470 of 500, second of seventeen, on its first appearance in the benchmark.

Latency. 5.08s, second fastest.

Strengths. A low published rate card on a single GET endpoint, and per-domain prices you can read before you sign up. 91 of the 100 sites returned on all five attempts, tied with Context.dev for the most after String. It returned 100% (as of the October 2026 benchmark run) against PerimeterX, AWS WAF and Kasada, and 97.9% against DataDome, tied with String.

Weaknesses. It returned nothing on three sites: temu.com, shop.lululemon.com and asda.com. 16 of its 2xx responses were not the requested page, against none for String. Akamai is its weakest wall at 87.0% in the October 2026 benchmark run. Its documentation lists no MCP server of its own. Scrape.do alternatives compares it with the field.

Context.dev: one credit a page, and a climb from eighth to third

Pricing. As of November 2026, Developer is $20 for 10,000 credits, Pro is $90 for 100,000, and one credit is one scrape whatever the page. That works out at $0.90 per 1,000 pages, flat, with overage at $2.00 per 1,000 on Pro. Most failed requests are not billed, so $0.90 is already the price of a returned page.

Benchmark success. 93.0%, 465 of 500, third of seventeen. It placed eighth of sixteen in September at 72.0%, and the 21.0-point gain is the largest in the run.

Latency. 10.96s, fourth of seventeen.

Strengths. The simplest pricing in the field, with rendering and anti-bot bypass inside the one credit, and a free tier of 1,000 credits a month with no card. In the October 2026 benchmark run it returned 100% against DataDome, the only provider to do so, up from 43.2% in September.

Weaknesses. Most failed requests are not billed, but a target's 404 is billed at the base price. It returned nothing on 6 of the 100 sites, mouser.com, ebay.com and kroger.com among them, and Akamai is its weakest wall at 79.0% in the October 2026 benchmark run.

Scrapfly: fourth on success, at more than four times String's latency

Pricing. As of October 2026, Pro is $100 a month for 1,000,000 credits. A datacenter HTTP fetch is 1 credit, residential is 25, rendering or the Unblocker adds 5. That is $0.10 to $2.50 per 1,000 pages. Failed requests are not charged, but a target's 404 is.

Benchmark success. 86.8%, 434 of 500, fourth of seventeen, up 0.6 points on September.

Latency. 19.62s, tenth of seventeen.

Strengths. The most complete public billing documentation in the field, SOC 2 Type II and ISO 27001, and a hosted MCP server with five tools. Only 5 of the 100 sites returned nothing, the third-lowest count after String's 0 and Scrape.do's 3, and it returned 96.7% (as of the October 2026 benchmark run) against AWS WAF.

Weaknesses. Its anti-bot mode can escalate the proxy pool without a published schedule, so the cost of a protected page is a range rather than a number. The credit table prices the Unblocker at 5 credits while a sample response on the same page shows an asp_cost of 30. Credits do not roll over. 35 of its 2xx responses were not the requested page.

ScrapingBee: last in August, fifth in October

Pricing. As of October 2026, Startup is $99 a month for 1,000,000 credits. The credit ladder is 1, 5, 10, 25 and 75, so a premium proxy with JavaScript is $2.475 per 1,000 and the stealth proxy is $7.425. Prices exclude VAT. Auto-Mode tries configurations cheapest first and charges only for the one that worked, or nothing if none did.

Benchmark success. 85.2%, 426 of 500, fifth of seventeen, up 12.2 points on September. It placed last of fifteen in August at 29.7%, and most of the climb since is an adapter correction: the August configuration was not ScrapingBee's strongest published path.

Latency. 20.30s, eleventh of seventeen.

Strengths. Auto-Mode with a max_cost ceiling is a genuinely good cost-control design, and a block reaches the caller as a free 500, unbilled. Its Cloudflare result in the October 2026 benchmark run is 97.3%, third in that column, up from 9.3% in August.

Weaknesses. Its own documentation routes "hard to scrape E-commerce websites" to the premium proxy, which is the 10 or 25 credit tier, so the realistic e-commerce rate is $2.475 per 1,000 rather than the $0.099 headline. It returned nothing on 9 of the 100 sites, and 41 of its 2xx responses were not the requested page (October 2026 benchmark run; pricing as of October 2026). ScrapingBee publishes no success rate of its own on its pricing page, FAQ or documentation.

Firecrawl: crawl a domain, and pay for the blocks

Pricing. As of October 2026, Standard is $99 a month billed monthly, or $83 a month billed annually, for 100,000 credits, one credit a page whatever the configuration. The pricing page defaults to the annual view, so check the toggle.

Benchmark success. 81.2%, 406 of 500, sixth of seventeen. 80 of the 100 sites returned on all five attempts, the fourth-highest count after String, Scrape.do and Context.dev.

Latency. 8.87s, third fastest.

Strengths. Crawl, map and extract in one product, and the flattest credit model of any vendor here: even its stealth escalation costs the same one credit. It returned 100% (as of the October 2026 benchmark run) against PerimeterX, tied with Scrape.do for the top of that column, and 98.7% against Cloudflare, tied with String.

Weaknesses. It charges for a request the target refuses. At its 81.2% success rate in the October 2026 benchmark run, that can turn $0.99 per 1,000 into $1.22 per 1,000 usable pages. It returned nothing on 17 of the 100 sites, more than Scrapfly or ScraperAPI. Credits do not roll over below annual Scale.

Zyte: the vendor sets your price tier, not you

Pricing. As of October 2026, five difficulty tiers, assigned automatically. At a $100 commitment an HTTP response costs $0.10 to $0.95 per 1,000 and a browser response $0.75 to $12.00. Bans are free. For Zyte's automatic extraction against Diffbot's, see Diffbot alternatives.

Benchmark success. 79.6%, 398 of 500, seventh of seventeen, up 11.6 points on September.

Latency. 14.43s, fifth of seventeen.

Strengths. Proxies, rendering and residential routing are all included in whichever tier your site lands in, so there are no per-feature surcharges to track. Its Cloudflare result rose from 58.7% to 92.0% between the September and October 2026 benchmark runs, and it returned 100% of the Kasada-protected sites.

Weaknesses. Zyte assigns the tier, reviews it quarterly and gives two weeks' notice of a change, and the per-site lookup needs an account. Akamai is its weakest wall at 68.0%, and it returned nothing on 14 of the 100 sites in the October 2026 benchmark run. Zyte API does not log in to sites, which it says plainly rather than leaving you to discover it.

Apify: a marketplace of prebuilt scrapers, and a slower second run

Pricing. No plan near $100. Starter is $19 a month (as of October 2026) and Scale $199, and the plan fee is itself spendable usage. Web Fetch costs $1.50 per 1,000 calls on Starter, $1.25 on Scale and $1.00 on the $999 Business plan, so $100 of monthly spend on Starter buys about 66,700 calls. Compute is $0.20 per unit on Starter and $0.16 on Scale. The Unblocker proxy is $1.50 per 1,000 requests.

Benchmark success. 79.4%, 397 of 500, eighth of seventeen, up 2.0 points on September.

Latency. 24.87s, fourteenth of seventeen, against 20.64s in September.

Strengths. A store of more than 100,000 Actors, which are prebuilt scrapers you rent rather than write, and they return structured fields instead of page content. Our Apify alternatives comparison covers the options when no Actor fits your site. Web Fetch charges only on a successful fetch and retries inside a request are free. In the October 2026 benchmark run it returned 100% of the Kasada-protected sites and 85.3% against DataDome.

Weaknesses. Unused prepaid usage expires at the end of the billing cycle rather than rolling over. A 404 page that Web Fetch converts to Markdown counts as a success and bills. It returned nothing on 12 of the 100 sites, and nothing at all on the single Fastly-protected target. We cannot tell you which Apify product the harness called, because the adapter lives in the benchmark repo rather than in the published data, so read 79.4% as Apify's adapter rather than as a named product's rate.

ScraperAPI: from third to ninth

Pricing. As of October 2026, no plan near $100: Hobby is $49 for 100,000 credits and Startup is $149 for 1,000,000. Startup is nearer to $100. A standard page is 1 credit, Amazon 5, Google and Bing 25, LinkedIn 30, and anti-bot bypass adds 10. A bypassed page therefore costs 11 credits: $1.64 per 1,000 at Startup or $5.39 at Hobby.

Benchmark success. 76.4%, 382 of 500, ninth of seventeen. It placed third of sixteen in September at 84.0%, so it fell 7.6 points. That September figure was itself a 19.8-point adapter correction on August's 64.2%.

Latency. 15.19s, sixth of seventeen.

Strengths. A max_cost parameter caps what any single request may spend, which no other vendor here offers. Blocked pages are not billed. It is third in the Akamai column at 81.0% in the October 2026 benchmark run, behind String and Scrape.do.

Weaknesses. The Domain Cost Estimator lives in the dashboard, so you cannot price your list before you sign up. Its own pricing page offers "a 7-day trial and 5,000 API credits" in the header and "1,000 free API credits" in the FAQ. In the October 2026 benchmark run it returned all five attempts on only 52 of the 100 sites, and 70.7% against Cloudflare.

Bright Data: the largest proxy pool, and one of the slowest latency scores

Pricing. As of October 2026, no plan near $100. Web Unlocker is $1.50 per 1,000 successful requests pay as you go, with a free tier of 5,000 requests a month and a $499 Scale plan.

Benchmark success. 75.4%, 377 of 500, tenth of seventeen, up 0.8 points on September.

Latency. 27.88s, fifteenth of seventeen.

Strengths. Pool scale, a large compliance surface, and a hosted MCP server. Only 6 of its 2xx responses were not the requested page, the third-fewest after String's 0 and Context.dev's 5.

Weaknesses. Its latency score went from 15.62s in September to 27.88s in the October 2026 benchmark run, third-slowest. Its DataDome result recovered from 47.4% to 74.7%, still below eight providers, and DataDome covers 19 of the 100 sites. Its docs say premium domains bill higher at a rate visible only in the dashboard, and hard targets are exactly the premium-domain profile. Because the frontier rate is unpublished, Bright Data is excluded from every cheapest claim on this page. We cover where Bright Data falls short and what replaces it on its own page.

Decodo: every configuration has a published price, and a 20.6-point recovery

Pricing. As of October 2026, Decodo's scraping API is now its Web Data API. The $99 plan publishes four rates per 1,000 requests: $0.30 standard proxies, $0.60 standard with JavaScript, $0.70 premium proxies, $1.10 premium with JavaScript. Premium proxies are the default. Prices exclude VAT and billing is monthly. Decodo bills only requests that return a result, so the rate is already the price of a returned page.

Benchmark success. 71.2%, 356 of 500, eleventh of seventeen. It placed twelfth of sixteen in September at 50.6%, and the 20.6-point gain is the second largest in the run, after Context.dev's.

Latency. 28.29s, sixteenth of seventeen.

Strengths. The clearest configuration grid in the field. You can price a workload before signing up, which most of these vendors do not allow. Its result on the proprietary-defence group rose from 41.5% to 70.4% between the September and October 2026 benchmark runs, and it returned 100% of the Kasada-protected sites.

Weaknesses. Decodo's own page claims a 99.99% success rate; we measured 71.2% on this suite in the October 2026 benchmark run. Both numbers can be true of different target lists, and the difference is what the list is made of. 48 of its 2xx responses were not the requested page, the second-most in the run, and it returned nothing on 19 of the 100 sites. It beat String on four sites: yellowpages.com, marketwatch.com, barrons.com and kroger.com. The site-by-site String and Decodo results go through them.

Nimble: usage pricing, and a jump to enterprise

Pricing. As of October 2026, Extract, Crawl and Map cost $1.00 per 1,000 requests, Search $1.10, Extract Template $3.00. The free tier is 5,000 requests a month. Named plans begin at $2,500 a month billed annually.

Benchmark success. 68.0%, 340 of 500, twelfth of seventeen, down 0.6 points on September.

Latency. 22.65s, thirteenth of seventeen.

Strengths. One usage meter across search, extract, crawl and media, with no credit conversion to learn. Its Cloudflare result rose again, from 62.7% to 68.0% between the September and October 2026 benchmark runs.

Weaknesses. There is nothing between usage pricing and a $2,500 plan, so a growing project has no middle tier. Nimble publishes no separate rate for protected pages. It returned nothing on 22 of the 100 sites in the October 2026 benchmark run, and its plan prices are as of October 2026.

Oxylabs: bandwidth billing, and no longer the PerimeterX leader

Pricing. Oxylabs now sells one subscription that covers all its products. On Basic at $100 a month (as of November 2026), Web Unblocker costs $6.00 per GB, about 16 GB; Starter is $15 at $7.20 per GB. Its billing documentation counts every 2xx and 4xx target response as successful. Its scraping API draws on the same subscription but is priced per result: on Basic, $0.90 per 1,000 without JavaScript and $1.40 with it.

Benchmark success. 67.4%, 337 of 500, thirteenth of seventeen, down 1.6 points on September.

Latency. 16.62s, seventh of seventeen.

Strengths. A broad product line, and 91.1% against PerimeterX in the October 2026 benchmark run, still one of the stronger results on that wall.

Weaknesses. In August it led the PerimeterX column at 97.8%. In the October 2026 benchmark run Scrape.do and Firecrawl both returned 100% there and Oxylabs is joint sixth. It returned 16.7% against AWS WAF and nothing on 26 of the 100 sites. Bandwidth billing means there is no cost per page without a page-weight assumption nobody publishes. The "from $0.25" rate in its own navigation is the Enterprise rate for Amazon results, on plans from $2,500 a month.

Browserbase: browser infrastructure, not a page-retrieval API

Pricing. As of October 2026, Startup is $99 a month for 100 concurrent browsers, 500 browser hours then $0.10 an hour, and 10,000 Fetch calls then $4 per 1,000 with proxies.

Benchmark success. 43.0%, 215 of 500, fourteenth of seventeen, up 1.6 points on September.

Latency. 18.01s, eighth of seventeen.

Strengths. The best product here for agents that click, log in and fill forms, and Stagehand is the most widely used framework of its kind.

Weaknesses. Advanced Stealth is on the custom Scale plan only; every self-serve tier gets Basic. It returned nothing on 53 of the 100 sites, tied with ZenRows for the most in the run, and 6.7% against Cloudflare, the lowest on that wall. The benchmark measures page retrieval, which is not what Browserbase is built for, and the 43.0% should be read that way.

ZenRows: fixed credit weights, and a pricing page that shows the annual rate

Pricing. As of October 2026, the docs table is the one to read. Launch L2 is $99 a month for 500,000 credits, and the weights are fixed on every plan: 1 standard, 5 with JavaScript, 10 with premium proxies, 25 protected. A protected page costs $4.95 per 1,000. The marketing pricing page shows the annual-equivalent monthly price by default.

Benchmark success. 41.8%, 209 of 500, fifteenth of seventeen, up 0.6 points on September.

Latency. 21.91s, twelfth of seventeen.

Strengths. An MCP server, a CLI and SDKs on every plan including Free, and 5,000 credits a month with no card. Unused top-up credits roll over once; plan credits expire at renewal. Its Akamai result rose from 47.0% to 57.0% between the September and October 2026 benchmark runs, ahead of Oxylabs and Nimble.

Weaknesses. In the October 2026 benchmark run, 53 of the 100 sites returned nothing, tied with Browserbase for the most, 33.3% against Cloudflare, 17.8% on the proprietary-defence group, the lowest there, and nothing at all on the single Fastly target. SOC 2 and ISO 27001 are Enterprise-only.

ScrapingAnt: a monthly free tier, and the steepest credit table

Pricing. As of October 2026, no plan near $100: Enthusiast is $19 for 100,000 credits and Startup $49 for 500,000. The credit table runs 1 for a plain fetch, 10 for a rendered page, 25 for a residential fetch and 125 for a rendered page on a residential proxy. That last configuration, the one a protected site needs, is $12.25 per 1,000 at Startup.

Benchmark success. 40.0%, 200 of 500, sixteenth of seventeen, up 3.6 points on September.

Latency. 18.39s, ninth of seventeen.

Strengths. 10,000 free credits every month with no card, tied with Decodo's 10,000 free pages as the largest recurring free allowance in the free-tier table, plus an MCP server with three tools.

Weaknesses. In the October 2026 benchmark run, 7.4% against DataDome, the lowest on that wall, and 75 of its 2xx responses were not the requested page, the most in the run. It returned nothing on 47 of the 100 sites. Credits do not roll over.

Scrapingdog: a cheap standard fetch, and last in the run

Pricing. As of October 2026, Standard is $90 a month for 1,000,000 credits, which is $0.09 per 1,000 plain requests, the lowest published standard rate of the seventeen after Scrape.do's. JavaScript rendering costs 5 credits, a premium proxy 10, both 25. That makes a protected page $2.25 per 1,000. Failed, blocked and timed-out requests are refunded.

Benchmark success. 27.6%, 138 of 500, seventeenth of seventeen, down 18.0 points on September.

Latency. 31.52s, the slowest of the seventeen. It was also the slowest in September, at 26.55s.

Strengths. The second-cheapest published plain fetch in the field, after Scrape.do, and the credit weights are printed on the pricing page rather than buried.

Weaknesses. In the October 2026 benchmark run, 6.7% against PerimeterX, the lowest of any provider on that wall, and 47 of the 100 sites returned nothing. As in September, it was the only provider to miss databricks.com, which every other provider returned on all five attempts. The same page that publishes the multipliers also promises "no surprise multipliers".

Where the anti-bot walls decide it

The 100 targets sit behind eight defence categories. Four cover 63 of the sites, and they are where the field separates. Every figure is percent of requests that returned content.

Provider DataDome (19 sites) Akamai (20) Cloudflare (15) PerimeterX (9)
String 97.9 97.0 98.7 97.8
Scrape.do 97.9 87.0 93.3 100.0
Context.dev 100.0 79.0 96.0 97.8
Scrapfly 92.6 78.0 93.3 93.3
ScrapingBee 85.3 74.0 97.3 88.9
Firecrawl 85.3 80.0 98.7 100.0
Zyte 68.4 68.0 92.0 91.1
Apify 85.3 69.0 86.7 86.7
ScraperAPI 75.8 81.0 70.7 82.2
Bright Data 74.7 72.0 74.7 86.7
Decodo 65.3 68.0 73.3 86.7
Nimble 64.2 51.0 68.0 82.2
Oxylabs 67.4 53.0 68.0 91.1
Browserbase 31.6 28.0 6.7 73.3
ZenRows 52.6 57.0 33.3 73.3
ScrapingAnt 7.4 33.0 24.0 53.3
Scrapingdog 16.8 27.0 29.3 6.7

In the October 2026 benchmark run, two things stand out. PerimeterX is the wall with the widest spread of the four: Scrape.do and Firecrawl returned 100% of PerimeterX-protected pages, and Scrapingdog 6.7%. Cloudflare is close behind, from 98.7% for String and Firecrawl to 6.7% for Browserbase. And no provider leads everywhere. Context.dev leads DataDome at 100% against String's 97.9%, and Scrape.do and Firecrawl both beat String on PerimeterX, 100% against 97.8%.

Chart data
ProviderDataDome (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)
String97.9%97.0%98.7%97.8%100.0%100.0%100.0%100.0%
Scrape.do97.9%87.0%93.3%100.0%100.0%100.0%100.0%92.6%
Context.dev100.0%79.0%96.0%97.8%100.0%100.0%100.0%92.6%
Scrapfly92.6%78.0%93.3%93.3%96.7%86.7%40.0%83.0%
ScrapingBee85.3%74.0%97.3%88.9%63.3%100.0%100.0%88.1%
Firecrawl85.3%80.0%98.7%100.0%83.3%100.0%100.0%60.0%
Zyte68.4%68.0%92.0%91.1%70.0%100.0%100.0%84.4%
Apify85.3%69.0%86.7%86.7%63.3%100.0%0.0%80.7%
ScraperAPI75.8%81.0%70.7%82.2%76.7%53.3%100.0%76.3%
Bright74.7%72.0%74.7%86.7%73.3%66.7%100.0%75.6%
Decodo65.3%68.0%73.3%86.7%73.3%100.0%0.0%70.4%
Nimble64.2%51.0%68.0%82.2%40.0%86.7%100.0%81.5%
Oxylabs67.4%53.0%68.0%91.1%16.7%100.0%0.0%80.0%
Browserbase31.6%28.0%6.7%73.3%16.7%33.3%0.0%80.7%
ZenRows52.6%57.0%33.3%73.3%36.7%60.0%0.0%17.8%
ScrapingAnt7.4%33.0%24.0%53.3%13.3%53.3%100.0%74.8%
Scrapingdog16.8%27.0%29.3%6.7%13.3%20.0%0.0%46.7%
Success rate by anti-bot vendor. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

Why pricing is hard to compare across these providers

Seven things stop web scraping API prices from lining up.

  1. The unit differs. Some vendors bill per request, some per credit, some per gigabyte, Browserbase bills per browser hour, and Apify bills per event or per compute unit. A credit is worth a different amount at every vendor and in every configuration.
  2. Credit weights vary by 125x. A protected page is 25 credits on ZenRows and ScrapingBee, 11 on ScraperAPI, 125 on ScrapingAnt, and 1 on Firecrawl and Context.dev.
  3. Some vendors price by site, not by setting. Zyte assigns a difficulty tier per website. ScraperAPI charges 5 credits for Amazon, 25 for Google and 30 for LinkedIn regardless of configuration.
  4. Browser meters are a separate model. Browserbase and String both sell browser time on bandwidth and duration, which no per-page rate captures.
  5. Failure billing splits the field. No vendor here bills a plain failed attempt by default, but twelve of the seventeen bill a target's own 404 page, String and Scrape.do included. Firecrawl, Oxylabs and Decodo also bill a returned 403, so on a list full of blocks those three list prices understate the real one.
  6. Annual rates pose as monthly. ZenRows and Firecrawl both show an annual-equivalent monthly price by default. Compare a vendor's annual rate to another's monthly rate and every conclusion after that is wrong.
  7. Some of the bill is unpublished. Bright Data's premium-domain rate and Scrapfly's ASP escalation are both real charges with no printed schedule.

What $100 a month buys

  • Scrape.do: Pro at $99 buys 1,250,000 plain datacenter requests at about $0.08, or 50,000 residential pages with a browser at about $1.98 (per vendor pricing, October 2026)
  • Context.dev: Pro at $90 buys 100,000 pages at $0.90 per 1,000, protection included (per vendor pricing, October 2026)
  • Scrapingdog: $90 buys 1,000,000 plain fetches at $0.09, or 40,000 protected pages at $2.25 (per vendor pricing, October 2026)
  • Decodo: $99 buys about 141,000 premium-proxy requests at $0.70, or 90,000 with JavaScript at $1.10 (per vendor pricing, October 2026)
  • Firecrawl: $99 buys 100,000 credits at $0.99, or about 81,200 usable pages once blocks are counted (per vendor pricing, October 2026)
  • String: $99 (as of October 2026) buys 618,750 plain fetches at $0.16, or 110,000 protected pages at $0.90 (per String pricing)
  • Scrapfly: $100 buys 1,000,000 datacenter fetches at $0.10, or 40,000 residential at $2.50 (per vendor pricing, October 2026)
  • ScrapingBee: $99 buys 1,000,000 plain fetches at $0.099, or 40,000 premium rendered pages at $2.475 (per vendor pricing, October 2026)
  • Apify: no $100 plan; the plan fee is spendable, so $100 buys about 66,700 Web Fetch calls at the Starter rate of $1.50 per 1,000 (per vendor pricing, October 2026)
  • ZenRows: $99 buys 500,000 plain fetches at $0.20, or 20,000 protected pages at $4.95 (per vendor pricing, October 2026)
  • Browserbase: $99 buys 500 browser hours plus 10,000 Fetch calls, then $4 per 1,000 with proxies (per vendor pricing, October 2026)
  • Nimble: usage priced, so $100 buys about 100,000 Extract requests at $1.00 per 1,000 (per vendor pricing, October 2026)
  • ScraperAPI: no $100 plan; Startup at $149 buys about 90,900 bypassed pages at $1.64 per 1,000, and Hobby at $49 buys 9,091 at $5.39 (per vendor pricing, October 2026)
  • ScrapingAnt: no $100 plan; Startup at $49 buys 4,000 rendered residential pages at $12.25 per 1,000 (per vendor pricing, October 2026)
  • Oxylabs: Basic at $100 buys about 16 GB of Web Unblocker traffic at $6.00/GB, a unit that resists a per-page figure (per vendor pricing, October 2026)
  • Zyte: a $100 commitment, priced by a per-site tier you cannot see without an account (per vendor pricing, November 2026)
  • Bright Data: no plan near $100, and it prices in a unit that resists a per-page figure (per vendor pricing, October 2026)

String is not the cheapest per page. Decodo quotes a lower rate for a protected page, Context.dev the same $0.90, Scrapingdog is 1.8x cheaper on a plain fetch, and Scrape.do's plain rate is about half of String's. The argument for String is the other column: at 98.6% against Scrapingdog's 27.6% in the October 2026 benchmark, the cheaper rate only applies to the pages that came back.

Which web scraping API should you pick?

  • Pick String when the list is protected and a missing page is a failed job rather than a retry.
  • Pick Scrape.do when you want the closest rival on success and a low published rate card, and can accept that a target's 404 bills.
  • Pick Scrapfly when you want several APIs on one key and can live with 19.62s.
  • Pick ScraperAPI when per-request cost caps matter more than the last points of success.
  • Pick Firecrawl when the job is crawling a domain into markdown, and budget for the blocks.
  • Pick Apify when someone has already written the scraper for your site and you want structured fields.
  • Pick Bright Data for proxy scale and an enterprise compliance surface, unless latency matters.
  • Pick ScrapingBee when cost control matters, for Auto-Mode's escalation ladder.
  • Pick Context.dev when one flat credit per page should include the protection, and for DataDome-heavy lists.
  • Pick Oxylabs when bandwidth billing suits your page weights better than a per-page rate.
  • Pick Nimble when search, crawl and extract should run off one usage meter.
  • Need search results, not pages? The best web search APIs compares nine search APIs on index, output and price.
  • Pick Zyte when you would rather the vendor price each site than configure it yourself.
  • Pick Decodo when you need to price a workload exactly before you sign up.
  • Pick Scrapingdog when the targets are unprotected and volume is the whole problem.
  • Pick Browserbase when the agent has to drive a browser, not read a page.
  • Pick ZenRows when you want an MCP server and a CLI on a free plan.
  • Pick ScrapingAnt when you want a large monthly free allowance to prototype against.
  • Leaving WebScrapingAPI or another API not listed here? It was not in the October 30 run, so this page does not rank it. The seventeen above are the tested field, and how to evaluate a web scraping API shows how to put your current provider through the same test on your own URLs.

FAQ

Which web scraping API is easiest to get started with?

Firecrawl, Context.dev and String need one HTTP call and no configuration decisions. Firecrawl and Context.dev charge one credit per page whatever the site, so there is no credit table to learn. String publishes four rates and picks the path for you. The vendors that take longest to start are the ones where the first request needs a configuration choice you cannot price yet: ScrapingAnt has a six-row credit table, and Zyte prices by a tier you cannot see without an account.

Which web scraping API is best for beginners?

Start on a monthly free tier so a mistake costs nothing. ScrapingAnt gives 10,000 credits a month, ZenRows and Nimble 5,000 requests a month, Firecrawl 1,000 credits a month, all without a card.

Then check the benchmark before you commit money. On 95 of the 100 sites in this run, at least one provider returned the page on all five attempts while at least one other returned nothing at all, so the vendor you start on decides the outcome on almost the whole list. ScrapingAnt and ZenRows returned nothing on 47 and 53 of those 100 sites, so a free tier that works on easy pages is not evidence about hard ones.

Which web scraping API has the best documentation?

Judged on what the docs tell you before you pay, Scrapfly and ZenRows are the most complete: both publish the full credit table, the failure-billing rule, the rollover policy and the escalation behaviour in one page. ScrapingBee's documentation publishes a per-status-code billing table, which nobody else does. The weakest are the ones where a real charge has no published schedule: Bright Data's premium-domain rate and Scrapfly's own ASP escalation.

Is there a good web scraping API with a REST endpoint and no SDK required?

All seventeen are plain HTTP. ScrapingAnt, ScrapingBee, Scrapingdog, ScraperAPI, Scrape.do and Apify's Web Fetch all take a single GET with the URL as a query parameter, so curl is enough. String, Firecrawl, Decodo and Zyte take a POST with a JSON body and an API key in a header, which is still one curl command. Nimble and Browserbase are the two where the interesting features sit behind their own clients: Browserbase's browser control expects Playwright, Puppeteer, Selenium or Stagehand.

What is the best web scraping API for a startup on a budget?

At the $100 tier, Decodo has the lowest published rate for a protected page at $0.70 per 1,000 on premium proxies, and it placed eleventh on the October run at 71.2%. Context.dev charges $0.90 with rendering and anti-bot bypass included in the one credit and placed third at 93.0%. String's premium rate is also $0.90 (as of October 2026), and it placed first at 98.6%. None of the three bills a plain failed attempt, so the rate is close to the price of a returned page and the real difference is coverage: String returned 493 of 500 requests, Context.dev 465 and Decodo 356.

If the targets are unprotected, Scrape.do at about $0.08 per 1,000 and Scrapingdog at $0.09 have the lowest plain rates here. Do the arithmetic on success rate before the arithmetic on rate: at 27.6%, Scrapingdog's cheap plain fetch fails on more than seven in ten requests to a fixed target list at any budget.

ScraperAPI vs ZenRows vs ScrapingBee, which should I use?

The October 2026 run reordered this question again. ScrapingBee, at 85.2%, is now fifth of seventeen and ahead of ScraperAPI, which fell to ninth at 76.4%. ZenRows is fifteenth at 41.8%, so both returned far more pages than it did: 426 and 382 of 500 against 209.

On cost for a protected page, ScrapingBee charges $2.475 per 1,000 on its $99 Startup plan and ZenRows $4.95 on Launch L2. ScraperAPI charges $1.64 for a bypassed page on its $149 Startup plan and $5.39 on its $49 Hobby plan. ScrapingBee is the pick for coverage and cost control through Auto-Mode, ScraperAPI for the lower latency score, 15.19s against 20.30s, and per-request cost caps, and ZenRows for the free plan and the agent tooling.

Which web scraping API works best on Cloudflare-protected sites?

String and Firecrawl both returned 98.7% (as of the October 2026 benchmark run) of requests across the 15 Cloudflare-protected sites in the suite. ScrapingBee followed at 97.3%, Context.dev at 96.0%, and Scrape.do and Scrapfly at 93.3%. At the other end, Browserbase returned 6.7%, ScrapingAnt 24.0% and Scrapingdog 29.3%. Cloudflare runs from 98.7% to 6.7% in this run, a 92.0-point spread, so it is one of the most useful columns to check against your own target list.

Can I verify these numbers?

Yes. The harness is public, including the 100 targets, the pass rule and every provider adapter, and it runs with your own API keys. The full leaderboard and methodology are on /benchmark. Pricing on this page was checked against each vendor's own pages on the dates given at the top.

Sources

Benchmark figures: the October 30, 2026 run, 100 targets, 5 attempts, 17 providers, 8,500 requests, written up in the October 2026 benchmark post, with raw results. Data modules and leaderboard: /benchmark. The September 16 and August 11, 2026 runs, used here only for the comparisons between runs, are written up here and here. Harness: github.com/usestring/web-data-frontier-benchmark.

Pricing and documentation, checked October 27 or October 28, 2026, and for Context.dev, Oxylabs, ScraperAPI and Zyte on November 17, 2026: String, Scrape.do and its request cost docs, Scrapfly, ScraperAPI, Firecrawl, Apify, Bright Data, ScrapingBee, Context.dev, Oxylabs Web Unblocker and scraping API, Nimble, Zyte, Decodo, Scrapingdog, Browserbase, ZenRows, ScrapingAnt.

Billing rules: Firecrawl, Scrapfly, Zyte, Bright Data, ScraperAPI, ScrapingAnt, ScrapingBee, Decodo, Apify, Oxylabs.

Related: best e-commerce scraping APIs, best web scraping tools, Firecrawl alternatives, Bright Data alternatives, Oxylabs alternatives, ScraperAPI alternatives, Zyte alternatives, ZenRows alternatives.

Web Scraping API Pricing in 2026: 17 Providers ComparedUpdated November 11, 2026Best E-commerce Scraping APIs for Price Monitoring (2026)Updated November 11, 2026Best Web Scraping Tools 2026: 13 Compared, Free and PaidUpdated November 11, 2026
Get your API key →Explore the Web Access API