String vs ScrapingBee (2026): 100 sites compared
Which is better, String or ScrapingBee?
String returned verified content on 98.6% of requests in the open Web Data Frontier Benchmark. ScrapingBee returned 85.2%. The October 30, 2026 run covered 100 real sites with five attempts each.
- Choose String if your list is varied and protected. In the October 2026 benchmark, String returned 98.6% of requests and ScrapingBee 85.2%, with no shutouts to ScrapingBee's 9.
- Choose ScrapingBee if your sites already work and prepaid unit cost matters, or you want its Google, Amazon, Walmart, and YouTube APIs.
- Do not switch if you need a SOC 2 Type II report. ScrapingBee publishes one and String has none.
That gap is 13.4 points, down from 24.0 in the September run and 67.3 in the August run, and the reasons matter. The August 2026 run sent ScrapingBee's default JavaScript path rather than its strongest published configuration, and it scored 29.7%. The September 2026 run corrected that, and ScrapingBee moved to 73.0%. Read that 43.3-point jump as our adapter catching up rather than as a product change. The October 2026 run scores ScrapingBee on its final HTTP status rather than the status before a redirect, and its 12.2-point rise to 85.2% came with that fix. Pick String when protected pages have to come back with no manual proxy tuning. Pick ScrapingBee for lower prepaid pricing, explicit configuration control, dedicated data APIs, and Auto Mode's cost ceiling.
TL;DR
- In the October 2026 benchmark, String passed 493 of 500 requests, or 98.6%. ScrapingBee passed 426, or 85.2%.
- ScrapingBee returned nothing on 9 of 100 sites. String passed 8 of those 9 on every attempt.
- ScrapingBee beat String on 4 sites: Kroger, 5 of 5 against 2, and Yellow Pages, MarketWatch, and Barron's, 5 of 5 against 4.
- In the October 2026 benchmark, String's failure-aware latency score was 4.24 seconds, the fastest in the run. ScrapingBee's was 20.30 seconds, eleventh of seventeen.
- On the 72 sites both products returned in full, ScrapingBee took twice as long or worse on 52 of them and three times as long or worse on 34.
- ScrapingBee Startup is $99 per month (as of October 2026) for 1,000,000 prepaid credits that last one month. String Growth is $99 per month (as of October 2026), and the fee is added to your balance as usage that rolls over.
- ScrapingBee's default JavaScript request costs 5 credits, premium plus JavaScript costs 25, and stealth costs 75.
- The benchmark harness is public and accepts your own API keys.
| String | ScrapingBee | |
|---|---|---|
| Product type | Unblocker: fetch, search, sitemap, remote browser | HTML scraping API plus dedicated search, retail, AI, screenshot, and extraction tools |
| Benchmark success | 98.6% (493/500), 1st of 17 | 85.2% (426/500), 5th of 17 |
| Latency score | 4.24s, 1st | 20.30s, 11th |
| Sites with no successful attempt | 0 of 100 | 9 of 100 |
| $100-tier billing | Growth: $99, added to your balance as usage at $0.16 to $3.25 per 1,000 successful requests | Startup: $99 prepaid, 1,000,000 credits, 100 concurrent requests, excluding VAT |
| Failure billing | Blocked requests are free; any status the site sends back, such as a 404, bills | 200, 404, and 410 responses bill; other failures are free |
| Automatic escalation | Built into the endpoint | Auto Mode chooses rendering and proxy strength, with an optional cost cap |
| MCP and integrations | Hosted MCP registry entry | Hosted MCP, CLI, LangChain, n8n |
| Where it wins | Measured coverage, latency, automatic retrieval on hard targets | Prepaid price, manual controls, Auto Mode, dedicated APIs, SDK and integration breadth |
How we tested
We built the benchmark and sell the product that ranks first. The test is public so buyers do not have to trust our summary. The targets, methodology, provider adapters and raw results are available to inspect and rerun.
Each provider received the same 100 URLs five times. A response passed only when it contained a marker from the real page. A captcha or challenge page that returned HTTP 200 failed.
This page has been rewritten against the October 30, 2026 run. An earlier version reported 29.7% for ScrapingBee and carried a long caveat explaining that the adapter used the default JavaScript path rather than premium proxies, stealth proxies or Auto Mode. That caveat was spent in September, when the run began sending every provider through its strongest published configuration and ScrapingBee's result rose to 73.0%. The honest reading is that the August figure measured our adapter and the later figures measure the product. One more harness change landed for October: ScrapingBee is now scored on its final HTTP status rather than the status before a redirect, and it scored 85.2%.
What each product is
ScrapingBee is a configurable scraping platform. Its HTML API exposes JavaScript rendering, premium and stealth proxies, country selection, sessions, custom headers and cookies, screenshots, CSS or XPath extraction, AI extraction, and browser actions. It also has a proxy mode for tools that expect an HTTP or SOCKS proxy.
The product surface extends beyond generic page retrieval. ScrapingBee offers Fast Search, Google, Amazon, Walmart, and YouTube APIs, AI and LLM endpoints, a hosted MCP server, and a CLI that can crawl a domain or sitemap. The AI extraction API adds five credits to the underlying scrape and returns structured fields from a natural-language request.
String is a web access API for developers and AI agents that returns a page's content as Markdown, HTML, or JSON. It is narrower than ScrapingBee: one fetch endpoint takes the URL. Proxy selection, fingerprints, captcha handling, rendering, and retries happen behind the request. String also has /search, asynchronous sitemap discovery, a remote browser over CDP, and MCP tools. It does not expose ScrapingBee's proxy ladder or its catalog of dedicated retail and search APIs.
The same request in ScrapingBee and String
One job, done both ways: fetch a JavaScript-heavy product page and get its content back. Each request follows the vendor's own docs for that job, checked against those docs on October 15, 2026. Each one reads its key from an environment variable, such as $STRING_API_KEY.
curl "https://app.scrapingbee.com/api/v1?url=https%3A%2F%2Fwww.example.com%2Fproduct%2F123&mode=auto" \
-H "Authorization: Bearer $SCRAPINGBEE_API_KEY"
curl https://request.usestring.ai/v1/fetch \
-H "Authorization: Bearer $STRING_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.example.com/product/123", "format": "markdown"}'
ScrapingBee renders JavaScript by default and returns raw HTML. With mode=auto it tries its JavaScript, premium, and stealth tiers from cheapest to most expensive and bills only the tier that worked. The manual route is premium_proxy=true or stealth_proxy=true, at 25 or 75 credits with JavaScript, and the two routes cannot be mixed in one request. Markdown needs return_page_markdown=true. String takes the key in a header, picks the fetch path and proxy class for each request, and bills the path it used. Add "executeJS": true if you want to force a browser.
Success rate: String 98.6%, ScrapingBee 85.2%
In the October 2026 benchmark, String passed 493 of 500 requests. ScrapingBee passed 426, a gap of 67 successful responses across the same target list.
| Per-target outcome | String | ScrapingBee |
|---|---|---|
| Passed all 5 attempts | 95 | 76 |
| Passed 1 to 4 attempts | 5 | 15 |
| Passed no attempts | 0 | 9 |
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 |
ScrapingBee's 76 perfect targets include Amazon, Walmart, Target, Best Buy, Home Depot, Kroger, LinkedIn, Facebook, Instagram, Reddit, eBay, Etsy, Expedia, Zillow, Bloomberg, The New York Times, Wall Street Journal, Ticketmaster and GoodRx. That is a much broader footprint than the August run suggested, and it covers most of a normal retail and news workload.
The 9 shutouts are Temu, Lowe's, Realtor.com, Skyscanner, AutoTrader, Coupang, Google, Reuters and Booking.com. String passed 8 of those 9 on every attempt and returned four of five on Skyscanner, the remaining site in that group.
The partial column is the one worth reading closely. ScrapingBee returned content on some attempts and nothing on others for 15 of the 100 sites, against String's 5. A site that answers three times out of five does not look like a failure in a log; it looks like a gap in the data.
ScrapingBee beat String on four targets. On Kroger, String's weakest site, it returned all five attempts to String's two. On Yellow Pages, MarketWatch and Barron's it returned all five to String's four. The two September wins did not repeat: String returned all five attempts on Coupang and Idealista, and ScrapingBee returned none on Coupang and all five on Idealista.
Anti-bot coverage
The category split explains the result. In the October 30, 2026 benchmark run, ScrapingBee's configuration is strong on Cloudflare, Kasada and the single Fastly site, and weakest on AWS WAF and Akamai.
| Anti-bot system | Sites | String | ScrapingBee |
|---|---|---|---|
| Cloudflare | 15 | 98.7% | 97.3% |
| DataDome | 19 | 97.9% | 85.3% |
| Akamai | 20 | 97.0% | 74.0% |
| PerimeterX | 9 | 97.8% | 88.9% |
| AWS WAF | 6 | 100% | 63.3% |
| Kasada | 3 | 100% | 100% |
| Fastly | 1 | 100% | 100% |
| No named vendor | 27 | 100% | 88.1% |
ScrapingBee's Cloudflare result is the headline change across runs: 9.3% in August, 92.0% in September and 97.3% in October, on the same fifteen sites. Its Akamai rate of 74.0% covers twenty sites, the largest single group in the suite, and its AWS WAF rate of 63.3% is its lowest.
Speed: String leads on both measures
In the October 2026 benchmark, String's latency score was 4.24 seconds, the fastest of the seventeen. ScrapingBee's was 20.30 seconds, eleventh. The score uses the per-target p75 of successful attempts and charges a provider for targets it cannot return, so fast failures do not look like speed.
In August the raw mean attempt time told the opposite story, because ScrapingBee's many fast failures pulled its mean down. That is no longer true. The October mean attempt time is 3.76 seconds for String and 17.45 seconds for ScrapingBee, so String now leads on the raw measure as well as the failure-aware one.
The cleanest comparison excludes failure entirely. On the 72 sites both products returned on all five attempts, the median per-site time was 1.70 seconds for String and 5.05 seconds for ScrapingBee. ScrapingBee took twice as long or worse on 52 of those 72, and three times as long or worse on 34.
Pricing: prepaid credits vs included usage
ScrapingBee Startup is $99 per month for 1,000,000 prepaid credits and 100 concurrent requests, excluding VAT. Its credit system charges one credit for classic proxies without rendering, five with rendering, ten for premium without rendering, 25 for premium plus rendering, and 75 for stealth. The pricing page says plan credits "are valid for one month and don't roll over."
At full use of Startup, those weights translate to:
| ScrapingBee configuration | Credits/request | Pages included | Price per 1,000 |
|---|---|---|---|
| Classic, no JavaScript | 1 | 1,000,000 | $0.099 |
| Classic with JavaScript | 5 | 200,000 | $0.495 |
| Premium, no JavaScript | 10 | 100,000 | $0.99 |
| Premium with JavaScript | 25 | 40,000 | $2.475 |
| Stealth with JavaScript | 75 | 13,333 | $7.425 |
String Growth's $99 (as of October 2026) monthly fee is added to your balance as usage, not a fixed credit bundle. Usage per 1,000 successful requests is $0.16 for a request path on a standard proxy, $0.90 on a premium proxy, $0.80 for a browser on a standard proxy, and $3.25 for a browser on a premium proxy. Unused credit rolls over.
Neither product wins every workload. One hundred thousand classic JavaScript requests fit inside Startup for $99. As of October 2026, String Growth bills the same $99 for that count: $16.00 of usage on the standard request path, $80.00 on a browser with a standard proxy, or $90.00 on its premium-request path, all covered by the fee, and any of it you do not use rolls over. At 100,000 premium-plus-JavaScript pages, ScrapingBee Business has enough credits at $249. String Growth costs $325 for 100,000 successful requests if every page needs a browser on a premium proxy, so ScrapingBee is cheaper there, but $99 if the premium-request path returns them.
String can be cheaper at the strongest edge. One hundred thousand stealth requests need 7.5 million ScrapingBee credits, fitting the $599 Business+ plan. String's most expensive published path, browser plus premium proxy, is $325 at 100,000 successful requests, and the $99 fee counts toward it.
Both products bill the site's real answer and skip most failures. ScrapingBee bills HTTP 200, 404, and 410 responses; other failures are free. Auto Mode bills only the successful configuration it selects and costs zero credits if all allowed configurations fail. String bills a request when it gets the site's response back, whatever status the site sent, so a 404 bills. Blocked requests and errors on String's side are free. Two exceptions bill: a blocked request that sent custom headers, and a request to a site with an invalid certificate. On both products, a dead URL spends credit.
Where ScrapingBee wins
- Lower cost for premium-plus-JavaScript volume that String would serve on a browser with a premium proxy: $249 (as of October 2026) against $325 at 100,000 pages.
- Auto Mode exposes a cost cap and reports the selected credit weight in a response header.
- Manual control over rendering, premium and stealth proxy tiers, country, sessions, headers, cookies, screenshots, and browser actions.
- Dedicated Google, Amazon, Walmart, YouTube, search, and AI APIs.
- Hosted MCP, a feature-rich CLI, six documented SDK languages, and first-party LangChain and n8n integrations.
- Published SOC 2 Type II and GDPR claims on its product site. String has no SOC 2 report.
Where String wins
- 98.6% measured success against 85.2% in the October 30, 2026 benchmark run.
- 95 perfect targets against 76, and no shutouts against 9.
- 5 partial targets against 15, which is the difference between a complete dataset and one with holes in it.
- A 4.24-second failure-aware latency score against 20.30, and a lead on raw mean attempt time as well.
- One endpoint that selects the fetch path, proxy, and retries without a credit multiplier selected by the caller.
- Unused credit rolls over. ScrapingBee plan credits last one month.
Which should you pick?
Pick String when your target list is varied, protected, and incomplete data is the main risk. Pick ScrapingBee when the sites are known to work, prepaid unit cost matters, or you need its dedicated APIs and explicit controls. The September and October runs make ScrapingBee a real option in a way the August run did not, and the remaining gap is concentrated in two places: the 9 sites it cannot return at all, and the 15 it returns inconsistently. Check both lists against your own before you decide.
Switching from ScrapingBee to String
What carries over. A GET to app.scrapingbee.com/api/v1 keeps its bearer key and becomes a POST to String's /v1/fetch. Keep the URL list and the code that reads HTML. return_page_markdown=true maps to "format": "markdown", render_js to executeJS, and extract_rules or ai_extract_rules to a jsonSchema. premium_proxy, stealth_proxy, and mode=auto have no String equivalent, because String picks the path.
What you rebuild. The Google, Fast Search, Amazon, Walmart, and YouTube APIs, Proxy Mode, sessions, and screenshots of a CSS selector. String's /search endpoint covers live Google results, and /v1/fetch takes screenshots and runs browser actions, but it returns pages rather than parsed retail results.
Integrations to reconnect. ScrapingBee publishes Python and Node SDKs, a CLI, a hosted MCP server, and integrations for n8n, Make, Zapier, and LangChain. 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. Take the URLs that fail on ScrapingBee today, or that only return on the 75-credit stealth tier, and run them through String. In the October 2026 benchmark, ScrapingBee returned nothing on 9 of the 100 sites, and String returned 8 of those on every attempt. Compare pages returned and cost per usable page, then 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. If you are weighing more than two tools, the ranking of web scraping APIs uses the same benchmark.
FAQ
Is String better than ScrapingBee?
On this benchmark, yes: String passed 98.6% (as of the October 2026 benchmark run) against ScrapingBee's 85.2%, with no shutouts against 9. ScrapingBee beat String on four sites, led by Kroger. ScrapingBee has lower prepaid pricing, more manual controls, dedicated data APIs, and a SOC 2 Type II report that String does not have.
Was ScrapingBee tested in its strongest mode?
In the September and October 2026 runs, yes. The August run used ScrapingBee's default JavaScript path and scored 29.7%, which measured our adapter more than the product. The September run sent every provider through its strongest published configuration, and ScrapingBee scored 73.0%, the largest gain of any provider between those two runs. The October run also scores ScrapingBee on its final HTTP status rather than the status before a redirect, and ScrapingBee scored 85.2%.
Is ScrapingBee cheaper than String?
Often. ScrapingBee Startup includes 1,000,000 credits for $99 (as of October 2026); String Growth's $99 fee is added to your balance as usage. At full use, ScrapingBee's classic JavaScript path is $0.495 per 1,000 and premium plus JavaScript is $2.475. String Growth usage ranges from $0.16 to $3.25 per 1,000 successes. ScrapingBee's prices exclude VAT.
Does ScrapingBee charge for failed requests?
ScrapingBee bills responses with HTTP 200, 404, or 410 and does not charge other failures. Auto Mode charges only the configuration that works and zero credits if all allowed configurations fail. String does not bill blocked requests, but it bills a site's 404 and any other status the site sends back.
What is ScrapingBee Auto Mode?
Auto Mode tries classic, premium, and stealth proxy configurations with or without JavaScript rendering, starting with the cheapest. It stops at the first success. max_cost can keep it from trying expensive tiers, and a response header reports the selected credit weight.
Does ScrapingBee have an MCP server?
Yes. ScrapingBee hosts a remote MCP server for scraping, screenshots, search, and dedicated data APIs. String also hosts an MCP server with fetch, search, and sitemap tools.
Which sites did ScrapingBee fail entirely?
Nine of the 100: Temu, Lowe's, Realtor.com, Skyscanner, AutoTrader, Coupang, Google, Reuters and Booking.com. String returned eight of them on all five attempts and four of five on Skyscanner.
How can I verify these numbers?
Run the public benchmark repository with your own API keys. The October 30, 2026 results and every provider adapter are in the repository, and the full leaderboard is on /benchmark.