Web Scraping API Pricing in 2026: 17 Providers Compared
Last updated: November 11, 2026. Every rate on this page was checked against the vendor's own pricing page, billing docs and credit docs on October 27 or October 28, 2026, and Oxylabs' again on November 11, 2026. Success rates come from the October 30, 2026 run of the Web Data Frontier Benchmark: 100 bot-protected sites, five attempts each, 500 requests per provider, 17 providers.
How much do web scraping APIs cost?
A standard page fetch costs about $0.08 to $1.50 per 1,000 requests at the plan nearest $100 a month. For bot-protected pages, the configuration each vendor used in our benchmark costs $0.90 to $4.95 per 1,000 where the rate is fixed. Pick Scrape.do or Scrapingdog for easy pages, String or Context.dev at $0.90 for protected pages, and a flat-rate vendor such as Firecrawl or Nimble when your mix is unpredictable. String charges $0.16 standard and $0.90 premium on its $99 Growth plan, as of October 2026.
String is a web access API for developers and AI agents: one HTTP call fetches any URL, with proxies, anti-bot handling and JavaScript rendering done for you, and it bills only requests that return content. Sources: each vendor's pricing page, billing docs and credit docs, checked October 27 and 28, 2026, and the October 30, 2026 run of the Web Data Frontier Benchmark.
Ranges reach $7.43 where the cost depends on the target, because most vendors multiply the price by 8x to 25x when you turn on premium proxies or JavaScript rendering. Scrape.do has the cheapest standard rate at about $0.08, and Scrapingdog is next at $0.09. For protected pages, String's premium rate and Context.dev's flat rate are both $0.90, the lowest fixed price any vendor here puts on the configuration it was benchmarked with, and Firecrawl charges one credit for every configuration, $0.99 per 1,000 on its monthly Standard plan. This page lists the standard and premium rate for 16 of the 17 providers in the benchmark, the credit multipliers behind them, which failures each vendor still bills, and what the configuration it was tested with actually costs. The seventeenth, Oxylabs, bills per gigabyte and is covered separately.
Which one is cheapest depends on what you fetch (vendor pricing pages, checked October 27 and 28, 2026; success rates from the October 30, 2026 benchmark run; String as of October 2026):
- Mostly easy pages: Scrape.do ($0.08) and Scrapingdog ($0.09) have the lowest standard rates. String's $0.16 (as of October 2026) sits mid-table.
- Mostly protected pages: String and Context.dev, both $0.90. At the same price, String returned 98.6% (as of October 2026) of benchmark requests and Context.dev 93.0%, so String fills more of a fixed list.
- A mix you cannot predict: a flat rate keeps the bill predictable. Context.dev charges $0.90, Firecrawl $0.99 and Nimble $1.00 for every page, easy or protected.
- A vendor whose rate depends on the target, such as Zyte's site tiers or ScrapingBee's Auto Mode: the only reliable number is a trial on your own URLs.
TL;DR
Source: each vendor's pricing and billing pages, checked October 27 and 28, 2026, and the October 30, 2026 run of the Web Data Frontier Benchmark.
- Sticker prices are not comparable. Vendors bill per request, per credit, per GB, per browser-hour, or from prepaid platform usage, and a credit is worth different amounts per vendor and per configuration.
- The standard-to-premium jump is the number to check first. ZenRows, Scrapfly and Scrape.do multiply by 25, ScrapingBee by up to 75, ScrapingAnt by up to 125. Firecrawl, Context.dev, Nimble and Apify charge one rate for every page, and Bright Data lists one rate with an unpublished premium-domain exception.
- No per-request vendor that publishes a failure policy bills a plain failed attempt by default, but most bill some failures. Oxylabs, which bills per GB, counts every 2xx and 4xx response from the target as billable traffic, a 403 block included. Firecrawl charges a credit for a returned 403 or 404. String, Scrape.do, ScraperAPI, ScrapingBee, ZenRows, Zyte, Scrapfly, Decodo, Context.dev and Apify bill a 404. Browserbase publishes no failure policy.
- Zyte prices by website difficulty across five tiers, so the same HTTP request costs $0.10 to $0.95 per 1,000 at a $100 commitment, depending on the site.
- Bright Data lists $1.50 per 1,000, but its docs confirm "premium domains" bill at a higher rate it does not publish. Hard targets are exactly the premium-domain profile.
- A low success rate caps what money can buy. At Scrapingdog's 27.6% benchmark success, the lowest in the run, no budget returns more than 27.6% of the requests on a fixed protected list.
Standard vs premium: the rate that matters
Source: each vendor's pricing page, linked in the table, checked October 27 and 28, 2026; String's rates are as of October 2026.
Most vendors advertise their standard rate. Almost nobody scrapes at it. The pages worth paying for, retail, travel, social, real estate, sit behind anti-bot vendors, and fetching them takes JavaScript rendering, premium or residential proxies, or both. That configuration is what this table calls the premium rate.
All rates are USD per 1,000 requests at the paid self-serve plan nearest $100 a month by dollar distance, billed monthly. Standard means a plain HTTP fetch with the vendor's default proxy and no JavaScript. Premium means the vendor's documented configuration for protected pages. The benchmark column is the rate for the exact configuration each vendor's adapter sent in the October run.
| Provider | Plan | Standard $/1k | Premium $/1k | Benchmark config $/1k | Premium multiple |
|---|---|---|---|---|---|
| Scrape.do | Pro $99 | 0.08 | 0.79 residential, 1.98 with browser | 0.79 to 1.98+, residential pool | 10x to 25x |
| Scrapingdog | Standard $90 | 0.09 | 0.90 | 0.90 to 1.80, premium + stealth | 10x |
| ScrapingAnt | Startup $49 | 0.10 | 2.45 residential, 12.25 with browser | 2.45, residential | 25x to 125x |
| ScrapingBee | Startup $99 | 0.10 | 2.48, stealth 7.43 | 0.10 to 7.43, Auto Mode | 25x to 75x |
| Scrapfly | Pro $100 | 0.10 | 2.50 residential | 2.50 plus unpublished anti-bot fees | 25x |
| Zyte | $100 commitment | 0.10 to 0.95 by site tier | 0.75 to 12.00 browser, by site tier | 0.10 to 0.95, HTTP | difficulty-tiered |
| ScraperAPI | Startup $149 | 0.149 | 1.49, 3.725 with JS | 4.47, ultra premium | 10x to 25x |
| String | Growth $99 | 0.16 | 0.90 | 0.90 | 5.6x |
| ZenRows | Launch $99 | 0.20 | 4.95 | 4.95 | 25x |
| Decodo | $99 plan | 0.30 | 1.10, premium proxies + JS | 1.10 | 3.7x |
| Browserbase | Startup $99 | 0.50 | 4.00 with proxies | 4.00 | 8x |
| Context.dev | Pro $90 | 0.90 | 0.90 | 0.90 | flat |
| Firecrawl | Standard $99 | 0.99 | 0.99 | 0.99 | flat |
| Nimble | Pay as you go | 1.00 | 1.00 | 1.00 | flat |
| Apify | Starter $19 | 1.50 | 1.50 | 1.50, Web Fetch | flat |
| Bright Data | Pay as you go | 1.50 | 1.50 listed; premium domains higher, unpublished | 1.50 | flat, with exceptions |
Five flat-rate structures stand out. Firecrawl charges one credit for everything, including its enhanced proxy, so its $0.99 is the same for an easy blog and for a protected storefront. Context.dev includes "JS rendering, anti-bot bypass, or premium proxies" in one credit. Nimble lists $1.00 per 1,000 URLs, although its own rendering docs say "Non-rendering is cheaper" without a number. Apify's Web Fetch Actor charges $1.50 per 1,000 (as of October 2026) fetches on Starter, $1.25 on Scale and $1.00 on Business, and its pricing tab lists platform costs as included. Bright Data's Web Unlocker is a premium product priced flat at $1.50, with the premium-domain caveat covered below.
Five structures resist a single number. Zyte assigns each website one of five difficulty tiers automatically, so your rate depends on what you scrape, not what you configure. ScrapingBee's Auto Mode tries cheaper configurations first and charges only the one that worked, anywhere from 1 to 75 credits. Scrapingdog documents premium proxies and stealth mode at 10 credits each but does not say whether they add up when combined, which is how the benchmark ran it. ScraperAPI's credit docs price ultra premium at 30 credits and bot-protection bypass at 10, and neither page says whether the two stack. Scrape.do's benchmark adapter pins its residential pool, which is 10 credits a request or 25 with the browser, and its request cost docs list domains where it applies its own profile and price, from 10 credits to 200; its $0.08 standard rate is $99 over 1,250,000 credits, rounded.
Plan choice moves several of these numbers. ScraperAPI has no plan at $100: Startup at $149 is $49 away and Hobby at $49 is $51 away, and on Hobby the same ultra premium request costs $14.70 per 1,000 rather than $4.47. ScrapingAnt's neighbours are $49 and $249, Apify's are $19 and $199, and Bright Data's are pay as you go and $499. Annual billing changes others: Firecrawl Standard drops from $99 to $83 a month billed annually, and ZenRows' pricing page can show a pay-10-get-12 figure ($58) for a plan that costs $69 billed monthly. Every figure above is the monthly-billed rate.
How we tested what these configurations deliver
Source: October 30, 2026 run of the Web Data Frontier Benchmark.
Rates only matter next to delivery. The Web Data Frontier Benchmark sends each provider's public API against 100 bot-protected pages, five attempts each, 500 requests per provider. In the October 30, 2026 run, 17 providers ran the same 100 sites. The adapters are public, and the benchmark column above prices the exact request each adapter sends, so the price and the success rate describe the same request.
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 |
Mean duration per benchmark attempt
The table below is the mean wall-clock time across all 500 attempts per provider in the October 30, 2026 run. Failed attempts and timeouts are included at their observed duration. These are measured per-attempt times, not throughput or deadline estimates. A provider that gives up quickly on a blocked page scores a low mean here, so read this table next to the success rates, never instead of them.
| Provider | Mean seconds per attempt |
|---|---|
| Browserbase | 1.65 |
| String | 3.76 |
| ScrapingAnt | 4.11 |
| Scrape.do | 4.43 |
| Firecrawl | 5.76 |
| Context.dev | 10.45 |
| Zyte | 11.87 |
| ZenRows | 12.46 |
| Oxylabs | 13.86 |
| Scrapfly | 15.89 |
| ScraperAPI | 15.91 |
| Scrapingdog | 16.98 |
| ScrapingBee | 17.45 |
| Bright Data | 25.18 |
| Decodo | 25.48 |
| Apify | 25.58 |
| Nimble | 31.27 |
Effective cost per usable page
Source: vendor billing docs, checked October 27 and 28, 2026, and the October 30, 2026 benchmark run; String's rates and 98.6% success are as of October 2026.
Dividing list price by success rate is the standard move here, and it is wrong for this field. The division only applies to vendors that charge for failed attempts, and none of the 15 vendors in the table that publish a failure policy bills a plain failed attempt by default. A vendor that bills only successes already prices the usable page, so its effective rate equals its list rate no matter how often it is blocked. What a low success rate costs those vendors is coverage, not money.
What varies is which failures count as successes. Firecrawl bills a 403 or 404 page it returns and bills nothing when it returns no result. If every one of its failed benchmark attempts had been a returned 403, its effective rate would rise from $0.99 to $1.22 per 1,000, so that row carries the range.
| Provider | Effective $/1k usable | Failure billing | Benchmark success |
|---|---|---|---|
| ScrapingBee | 0.10 to 7.43 | success only; 404, 410 and 413 bill | 85.2% |
| Zyte | 0.10 to 0.95 | success only; 404 bills | 79.6% |
| Scrape.do | 0.79 to 1.98+ | success only; 400, 404 and 410 bill | 94.0% |
| Scrapingdog | 0.90 to 1.80 | success only | 27.6% |
| Context.dev | 0.90 | success only; a 404 bills | 93.0% |
| String | 0.90 | success only; a 404 bills | 98.6% |
| Firecrawl | 0.99 to 1.22 | returned 403 and 404 bill; no result is free | 81.2% |
| Nimble | 1.00 | success only | 68.0% |
| Decodo | 1.10 | success only; a non-empty 403 or 404 bills | 71.2% |
| Apify | 1.50 | success only; a returned 404 bills | 79.4% |
| Bright Data | 1.50+ | success only, with exceptions | 75.4% |
| ScrapingAnt | 2.45 | success only | 40.0% |
| Scrapfly | 2.50+ | success only; 404 and other listed 4xx bill | 86.8% |
| Browserbase | 4.00 | not published | 43.0% |
| ScraperAPI | 4.47 | success only; 404 bills | 76.4% |
| ZenRows | 4.95 | success only; 404 and 410 bill | 41.8% |
The table is sorted by the low end of each range. A row that shows a range, or a plus sign for an unpublished component, does not earn a "cheapest" rank: its real rate depends on the targets you send.
String's row uses its premium fetch rate, because the benchmark's 100 targets are all bot-protected and that is the honest configuration to price. At its $0.16 (as of October 2026) standard rate String would sit near the top of this table, but that is not the rate the benchmark workload represents, so we do not quote it here. Against String's $0.90, Context.dev prices its benchmark configuration the same, at $0.90, and none prices it lower at a fixed rate. Ten price it higher at every point of their published range: Firecrawl, Nimble, Decodo, Apify, Bright Data, ScrapingAnt, Scrapfly, Browserbase, ScraperAPI and ZenRows. Scrapingdog's range starts at String's rate, and the ranges for ScrapingBee's Auto Mode, Zyte's site tiers and Scrape.do's residential pool span it.
What does 200,000 fetches a day cost per successful page?
String bills only successful requests, so its cost per successful page is its list rate. As of October 2026, per String pricing, 200,000 fetches a day (about 6 million a month) cost $32 a day on standard proxies and $180 on premium proxies on Growth, and $22 and $90 on Volume, the lowest self-serve rates. A browser request bills at a higher rate.
Which String plan fits 30 million pages a month?
Volume, at $999 a month, has String's lowest self-serve rates. As of October 2026, per String pricing, 30 million pages a month on Volume cost $3,300 as standard fetches, $13,500 on premium proxies and $15,000 as standard browser requests, so the share of pages that need a browser decides the bill. Enterprise, from $2,500 a month, sets a custom rate card for that volume.
Who bills a failed request
Billing rules, straight from each vendor's own pages, fetched October 27 and October 28, 2026.
Success only, 4xx pages not addressed. ScrapingAnt ("failed requests cost 0"), Nimble ("Only successful requests count toward your usage"), and Scrapingdog ("Failed, blocked and timed-out requests are automatically refunded"). None of these three says whether a target's own 404 page counts as a success.
Success only, but a returned error page bills. String does not bill a blocked request, but its pricing FAQ says "A 404 from the site is billed" because it is the site's real answer. ScraperAPI charges "for successful requests (200 and 404 status codes)". ScrapingBee bills 200, 404 and 410, and its docs table adds 413. ZenRows counts 404 and 410 as successful. Zyte passes a target's 404 through as a successful, billable response and does not bill a ban. Apify's Web Fetch charges nothing for failed requests, but "if the site responds with a 404 page" that page is still one fetch. Firecrawl bills a returned 403 or 404 at one credit. Decodo says you only pay for successful requests, but its response-code table bills a 403 or 404 when the response is not empty; its own 500, 524 and 613 failures never bill. Scrape.do's pricing FAQ says you "won't lose credits on timeouts, blocks, or errors," but its request cost docs count 2XX, 400, 404 and 410 responses as successful, so those bill. Context.dev's pricing page says "Most failed requests are not billed", but a 404 bills at the request's base price, and its free-credits docs say "successful and partial results are charged".
Success only, with conditions that switch it off. Scrapfly's pricing page says a failed request is "$0, never charged on error". Its billing docs are narrower: 404 and a list of other 4xx codes are excluded from failure protection, and if 30% or more of your scrapes over the last 24 hours (on at least 1,000 scrapes) are blocked without the Unblocker, failure protection switches off and failures bill. Bright Data's success-only rule switches off entirely when custom headers, cookies or manual "expect" elements are enabled on a zone: then 100% of requests bill, failures included.
Not published. Browserbase's Fetch API pricing says nothing about failed or error responses either way. Its row uses the list rate, unflattered and undivided.
The premium-domain problem
Source: Bright Data, Zyte and Scrapfly docs linked below, checked October 27, 2026 and October 28, 2026.
Bright Data's $1.50 deserves its own section because it is the table's most misleading-looking bargain. The Web Unlocker docs state that "premium domains" bill at a higher rate, that the price appears only in the zone's "Estimated cost" field, and that the domain list is updated quarterly. The public pricing page does not carry the premium rate at all. The domains that need an unblocker in the first place, large retail, social, and travel sites, are the premium-domain profile. So the $1.50 in every comparison table, ours included, is the rate for the domains you were least likely to need Bright Data for. We mark the row $1.50+. Price your actual domain list in their dashboard before you budget from any table. Our comparison of alternatives to Bright Data sets six providers against it, including Zyte with its public domain tiers.
Zyte has the same shape with more disclosure. Its five difficulty tiers are assigned automatically per website, reviewed quarterly, with two weeks' notice of any tier change, and the tier ladder is public: $0.10 to $0.95 per 1,000 HTTP responses at a $100 commitment. What is not public is which tier your target sits in until you send traffic. For a hard-target workload, budget toward the top of the ladder.
Scrapfly is the third. Its credit table prices a residential request at 25 credits, but its Unblocker may upgrade the proxy pool and add unpublished fees on some targets, and the sample response on its own pricing page shows an anti-bot cost of 30 credits. We mark the row $2.50+.
The credit decoder
Credit vendors publish one attractive per-credit price and vary the credits per request. These are the published multiplier tables, verified October 27 and October 28, 2026.
| Provider | Base | JS render | Premium proxy | JS + premium | Residential or stealth |
|---|---|---|---|---|---|
| ScrapingBee | 1 | 5 | 10 | 25 | 75 stealth |
| ZenRows | 1 | 5 | 10 | 25 | n/a |
| ScrapingAnt | 1 | 10 | n/a | n/a | 25 residential, 125 with browser |
| ScraperAPI | 1 | 10 | 10 | 25 | 30 ultra, 75 ultra + JS |
| Scrapingdog | 1 | 5 | 10 | 25 | 10 stealth |
| Scrapfly | 1 | 5 | n/a | n/a | 25 residential, 60 screenshot |
| Scrape.do | 1 | 5 | 10 residential | 25 | 10 to 200 on listed domains |
| Firecrawl | 1 | 1 | 1 | 1 | 1 |
| String | 1 | 5 browser | 5.6 | 20.3 browser premium | n/a |
String sells no credits. Its row shows the ratio between its four published per-1,000 rates on Growth, as of October 2026 per String pricing, so it reads on the same scale as the others.
Two practical rules fall out of this table. First, never budget from a vendor's per-credit price without knowing your configuration's multiplier: a $149 plan at 30 credits per request is a $4.47-per-1,000 plan. Second, a flat-credit vendor like Firecrawl is cheap for hard pages and expensive for easy ones, and a multiplier vendor is the reverse, so the right vendor depends on your mix.
The vendor you cannot put in the table
One benchmarked provider ran through a product that does not sell requests, and converting its unit would mean inventing a number, so it sits outside the table. Sources: the Oxylabs and Browserbase pricing pages linked below, checked October 27 and 28, 2026, and the October 30, 2026 benchmark run.
Oxylabs Web Unblocker bills per gigabyte under one subscription that now covers every Oxylabs product: $6.00 (as of November 2026) per GB on the $100 Basic plan, up to 16 GB, and $7.20 on the $15 Starter. Your per-page cost depends on page weight, which varies by an order of magnitude across sites. The same subscription buys Oxylabs' Web API /scrape endpoint per result, $0.90 per 1,000 on most sites at Basic and $1.40 with JavaScript, but the benchmark did not test that product. Its docs count every 2xx and 4xx response from the target as successful, so a 404 or a 403 consumes traffic. Oxylabs scored 67.4% on the benchmark through this product.
Browserbase sat in this section in August, priced per browser-hour. The benchmark now calls its Fetch API, which bills per call: $0.50 per 1,000 without proxies and $4.00 with proxies above the Startup plan's 10,000 included calls. The Startup card and the compare table on its pricing page both say $0.50 per 1,000 for the plain call; $1 is the Developer plan rate. Neither says whether the included calls cover proxied calls, so its row uses the $4.00 proxied rate.
Why a cheap rate can still cost you the project
Source: October 30, 2026 run of the Web Data Frontier Benchmark; prices checked October 27 and 28, 2026.
Effective cost only compares vendors that can return the page. Seven of the sixteen competitors in the benchmark failed more than one request in four. Scrapingdog, Browserbase, ZenRows, and ScrapingAnt failed more than half. For a success-billed vendor, failing is free for you and for them, but it does not get you the data: at Scrapingdog's 27.6% success rate, a fixed list of protected URLs returns 27.6% of its pages no matter what you spend. Price tells you the cost of the pages you get. Success rate decides whether you get the pages at all. To lower the bill without losing pages, see how to reduce web scraping costs.
Stated plainly, String's $0.90 per 1,000 (as of October 2026) premium fetches is less than ten of the sixteen other providers charge for the configuration they were tested with, and it comes with 98.6% success, the highest in the benchmark. Two others cleared 90%: Scrape.do at 94.0%, with a residential range of $0.79 to $1.98 that spans String's rate, and Context.dev at 93.0%, at the same flat $0.90. For the full ranking with every provider's strengths, see the best web scraping APIs comparison.
FAQ
Source for the figures below: vendor pricing pages checked October 27 and 28, 2026, and the October 30, 2026 benchmark run; String as of October 2026.
What does a web scraping API cost in 2026?
At the plan nearest $100 a month, standard fetches run about $0.08 to $1.50 per 1,000 requests across the 16 providers that price per request, per their pricing pages checked October 27, 2026 and October 28, 2026. The configurations the same providers used against bot-protected pages run $0.90 to $4.95 per 1,000 where the rate is fixed, and ranges reach $7.43 where the cost depends on the target. The spread comes from credit multipliers of up to 125x that most vendors apply for JavaScript rendering and premium proxies.
What is the cheapest web scraping API?
Scrape.do has the cheapest published standard rate at about $0.08 per 1,000 requests on its $99 Pro plan, and Scrapingdog is next at $0.09 on its $90 plan. For bot-protected pages, String's $0.90 per 1,000 (as of October 2026) premium fetch and Context.dev's flat $0.90 are the lowest fixed rates among providers that cleared 80% on our 100-site benchmark, at 98.6% and 93.0% success, with Firecrawl's flat $0.99 next. Scrape.do's residential pool starts lower, at $0.79, and reaches $1.98 with its browser, at 94.0% success.
Is String the cheapest web scraping API?
Not outright. Context.dev's flat $0.90 per 1,000 (as of October 2026) matches String's $0.90 premium fetch rate, and the ranges for Zyte, ScrapingBee and Scrape.do start lower, but ten of the other sixteen providers charge more for the configuration they were benchmarked with. String's $0.16 standard rate sits in the middle of the field, and its 98.6% benchmark success rate (as of October 2026) is the highest of any provider tested.
Do web scraping APIs charge for failed requests?
Not for a plain failure by default, under any per-request vendor that publishes a rule. Many do bill a target's own error page: Firecrawl bills a returned 403 or 404, String, Scrape.do, ScraperAPI, ScrapingBee, ZenRows, Zyte, Decodo, Context.dev and Apify bill a 404, and Scrapfly bills 404 and other listed 4xx codes. Bright Data bills every request on zones with custom headers or cookies. Browserbase publishes no failure policy.
Why do credit-based plans cost more than they look?
Because credits per request scale with configuration. On its pricing page (checked October 28, 2026), ScrapingBee's $99 plan is $0.10 per 1,000 at one credit per request and $7.43 per 1,000 at its 75-credit stealth configuration. Always compute price at the configuration your targets need, not the base rate.
Should I divide price by success rate to compare vendors?
Only for vendors that bill failed attempts, and no per-request vendor on this page that publishes a failure policy does so by default. For a success-billed vendor, a failed request costs nothing, so the effective rate equals the list rate. Dividing there invents a cost the vendor does not charge. The adjustment that does apply is for returned error pages: Firecrawl's range of $0.99 to $1.22 is that adjustment, from its billing docs checked November 17, 2026.
What does Bright Data's Web Unlocker really cost?
$1.50 per 1,000 requests pay as you go, or $1.30 per 1,000 above the 383,000 requests included in the $499 Scale plan, per its Web Unlocker pricing checked November 17, 2026. Its docs confirm premium domains bill higher at a rate shown only in the dashboard, and enabling custom headers or cookies switches a zone to billing all requests, failures included. Price your actual domains in their dashboard before budgeting.
Are annual prices comparable to monthly prices?
No. As of October 2026, annual billing discounts most plans: Firecrawl's Standard drops from $99 to $83 a month, and ZenRows' pricing page can show $58 for a plan that costs $69 billed monthly. Mixing bases skews any table. Every rate on this page is billed monthly. Check the billing toggle before trusting any vendor comparison, including this one.