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

String vs Decodo (2026): 100 protected sites

Logan Harless, Founder, String · Published August 31, 2026 · Updated November 2, 2026

Which is better, String or Decodo?

String won the measured fetch comparison. On the October 30, 2026 Web Data Frontier Benchmark, String returned verified content on 98.6% of 500 requests and Decodo 71.2%. Pick String for measured coverage and speed. Pick Decodo when its $1.10 per 1,000 premium-plus-JS rate and broader scraping platform matter more.

  • Choose String if coverage and speed decide it.
  • Choose Decodo if you want 100+ target templates, raw proxy pools, or browser actions in the same account.

TL;DR

  • Success rate in the October 30, 2026 run: String 98.6% (493/500), Decodo 71.2% (356/500), up from 50.6% in September
  • Latency score in the October 30, 2026 run: String 4.24s (first of 17), Decodo 28.29s (16th)
  • Clean targets: String 95 of 100, Decodo 54
  • Sites where nothing came back: String 0, Decodo 19, including 12 targets where Decodo's API returned HTTP 400 on every attempt
  • Decodo's clean wins: Yellow Pages, MarketWatch, and Barron's, each 5/5 against String's 4/5
  • Benchmark mode: universal target, premium proxy pool, JavaScript rendering, raw HTML
  • Price: Decodo's $99 plan includes about 90,000 premium-plus-JS successes at $1.10 per 1,000
  • Every number comes from a public harness you can run with your own keys
String Decodo
Product type Fetch, search, sitemap, and remote browser Web Data API, formerly the Web Scraping API, 100+ templates, proxies, Site Unblocker, search APIs, AI Parser, MCP
Benchmark success rate 98.6% (493/500) 71.2% (356/500), premium proxies plus JS
Latency score 4.24s, first of 17 28.29s, 16th of 17
Per-target outcome 95 clean, 5 partial, 0 blank 54 clean, 27 partial, 19 blank
Anti-bot highlights 100% AWS WAF, Kasada, Fastly and sites with no named vendor 100% Kasada, 86.7% PerimeterX, 73.3% Cloudflare and AWS WAF
Pricing basis Plan fee paid in as usage credit; blocked requests are free, a site's 404 bills; credit rolls over Monthly plan billed per request by proxy and rendering path; its own failures are free, a 2xx or 4xx that returns a result bills
Entry point First 20,000 standard fetches free Free plan, no card: up to 10,000 standard or about 3,300 premium-plus-JS requests
Agent tooling Hosted MCP and HTTP API MCP server, Markdown output, AI integrations, TypeScript tooling
Where it wins Measured coverage and latency Yellow Pages, MarketWatch, Barron's, Kroger, premium-plus-JS pricing, templates, formats, proxy breadth, ISO 27001

How we tested, and our conflict of interest

We built the Web Data Frontier Benchmark and sell the product that ranks first. The defense against that conflict is reproducibility. The targets and pass criteria, every provider adapter, and the raw results are public. A request passes only when its body contains an expected marker from the real page. A captcha or empty shell with HTTP 200 fails.

The Decodo adapter sends target: "universal", proxy_pool: "premium", and headless: "html". Through September it posted that body to the legacy Web Scraping API's /v2/scrape; for the October run it sends the same body through Decodo's Web Data API with the dashboard API key, and Decodo's 20.6-point rise came with that new endpoint. Decodo's parameter reference says premium proxies are for stronger anti-bot measures and headless: "html" enables JavaScript rendering. Its introduction recommends that combination for protected or difficult targets.

This is the strongest general-purpose Decodo path, returning raw HTML. It did not use one of Decodo's 100+ site-specific templates, a dedicated parser, browser actions, or location targeting. A template could do better on a supported target, but no one template spans the 100-site suite.

If Decodo believes a different general configuration is fairer, the adapter is one file and a pull request changes the next run. A Firecrawl engineer used that route in benchmark pull request 6, and the next run raised Firecrawl's result by 7.7 points.

Decodo pricing and billing were checked against its live pricing page, billing docs and response-code table on October 28, 2026, and other product claims against first-party pages on August 31, 2026. Performance figures are from the October 30, 2026 run.

What Decodo is

Decodo, formerly Smartproxy, sells both raw proxy infrastructure and managed scraping products. Its Web Data API, which replaced the Web Scraping API the benchmark ran through September, handles proxy rotation, browser rendering, anti-bot work, retries, and parsing behind one endpoint. It can return HTML, JSON, CSV, Markdown, XHR captures, or PNG screenshots, synchronously or asynchronously.

The product has 100+ target templates for search engines, ecommerce, social platforms, and other common sources. The universal Web target accepts any public URL. Per-request controls cover standard or premium proxies, JavaScript rendering, location, device, sessions, POST bodies, Markdown, XHR capture, and successful status codes. Decodo also documents browser actions for clicks, waits, and network-resource capture.

Outside the Web Data API, Decodo sells residential, mobile, ISP, and datacenter proxies, Site Unblocker, Fast Search API, specialized scraping APIs, an AI Parser, and a free MCP server. String is a fetch API for developers and data teams that returns the page behind one URL as Markdown, HTML, or JSON, even when bots block it. It is narrower than Decodo: one adaptive fetch endpoint, plus search, sitemap crawling, a remote browser over CDP, and MCP.

The same request in Decodo 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://data.decodo.com/v1/scrape \
  -H "Authorization: Bearer $DECODO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.example.com/product/123", "headless": "html", "markdown": true}'
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"}'

Decodo's Web Data API replaced the Web Scraping API the benchmark ran through September, and its migration guide says old and new keys do not work across the two. It returns a JSON envelope with the page in content and does not render JavaScript unless the request sends headless: "html". markdown: true converts the page. 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%, Decodo 71.2%

The benchmark sent 17 providers the same 100 URLs five times each. Most targets are protected retail, travel, news, real-estate, and social pages.

Provider Successful requests Success rate Latency score
String 493/500 98.6% 4.24s
Scrape.do 470/500 94.0% 5.08s
Context.dev 465/500 93.0% 10.96s
Scrapfly 434/500 86.8% 19.62s
ScrapingBee 426/500 85.2% 20.30s
Firecrawl 406/500 81.2% 8.87s
Zyte 398/500 79.6% 14.43s
Apify 397/500 79.4% 24.87s
ScraperAPI 382/500 76.4% 15.19s
Bright Data 377/500 75.4% 27.88s
Decodo 356/500 71.2% 28.29s
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
Accuracy against latency. Accuracy is the percent of requests that returned verified content; latency is the failure-aware mean per-target p75, in seconds. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

Decodo ranked 11th of 17 for success and 16th on the latency score. The score uses each target's p75 successful latency. A complete miss inherits that target's p75 from providers that did return content, or the 90-second timeout when nobody did. Fast failures do not improve it.

The 27.4-point success gap is meaningful because Decodo already had premium routing and browser rendering enabled. This is not a basic-proxy result.

Decodo wins Yellow Pages, MarketWatch, Barron's, and Kroger

Decodo passed Yellow Pages, MarketWatch, and Barron's on all five attempts; String passed four on each. On Kroger, Decodo passed three to String's two. Those are the four targets where Decodo beat String outright.

In the October 30, 2026 benchmark run, Decodo's strongest verticals were news and finance at 100%, ahead of String's 95.6%, and social platforms at 92.5%. It returned nothing at all across tickets and events, search engines, and government. Against named anti-bot vendors its best columns were Kasada at 100%, tied with String, and PerimeterX at 86.7%.

Foot Locker, its one win in September, was five of five for both products in October. There is no site in this run where Decodo returned every attempt and String returned none.

The measured coverage gap is 19 rescued targets

Outcome across 100 sites String Decodo
Passed all 5 attempts 95 54
Passed 1 to 4 attempts 5 27
Passed none 0 19

Decodo returned nothing on 19 sites: Temu, Mouser, Skyscanner, Yelp, Neiman Marcus, G2, StubHub, Ticketmaster, SeatGeek, Kayak, Google Search, Congress.gov, eBay, Amazon, AT&T, AXS, Roblox, arXiv and Bing. String passed 18 of those 19 on all five attempts and returned four of five on Skyscanner. Twelve of the 19, including Amazon, Ticketmaster, StubHub, SeatGeek, Google Search and Bing, are targets where Decodo's API returned HTTP 400 on every attempt, so part of the gap is Decodo's API rejecting requests rather than the targets blocking them.

Decodo also has 27 partial targets against String's 5. Retries improve its result on those, but they stretch completion time and leave a dataset that differs between runs.

In the October 30, 2026 run, the anti-bot columns show the coverage difference. Decodo passed 73.3% (as of the October 2026 benchmark run) of Cloudflare requests against String's 98.7%, 65.3% of DataDome against String's 97.9%, and 73.3% of AWS WAF against String's 100%. Its one parity result is Kasada, where both returned 100%. On Akamai, the largest group at twenty sites, Decodo rose from 57.0% in September to 68.0%, against String's 97.0%.

Pricing: Decodo wins on premium proxies plus JavaScript

Decodo's scraping API is now its Web Data API, and its current pricing separates four paths (checked October 28, 2026): standard proxies, standard plus JavaScript, premium proxies, and premium plus JavaScript. Premium proxies are the default, so a request that does not choose a pool bills at a premium rate. The benchmark used the last and most expensive path.

Monthly plan Standard Standard + JS Premium Premium + JS Premium + JS allowance
Free $0.50/1k $0.75/1k $1.00/1k $1.50/1k 3,300
$19 $0.50/1k $0.75/1k $1.00/1k $1.50/1k 12,600
$49 $0.40/1k $0.65/1k $0.75/1k $1.25/1k 39,200
$99 $0.30/1k $0.60/1k $0.70/1k $1.10/1k 90,000

The free plan requires no card. Decodo says you pay only for successful requests and never for its own 500, 524 and 613 failures. Its response-code table also counts a 2xx or 4xx response as successful when a result comes back, so a block page with a body can bill. Paid plans include a 14-day money-back option.

String's plan fee is paid in as usage credit. Starter is $19 per month (as of October 2026), which includes $19 of usage at $0.25 per 1,000 standard fetches or $2.40 per 1,000 premium fetches. Growth is $99 per month, which includes $99 of usage at $0.16 or $0.90 (as of October 2026). Usage above the included amount bills at the same rates, and browser paths cost more. Blocks are free, a site's 404 bills, and unused credit rolls over.

At 100,000 calls against the benchmark target mix:

Assumption Monthly cost Cost per 1,000 usable pages
Decodo $99, premium + JS 71,200 successes fit its 90,000-request allowance, with room for billed 2xx and 4xx failures $99.00 $1.39
String Starter, standard fetch 98,600 successes at $0.25/1k, above the $19 included $24.65 $0.25
String Growth, premium fetch 98,600 successes at $0.90/1k ($88.74), inside the $99 fee $99.00 $1.00

This is a model, not a bill. Decodo's 48 failed attempts that came back as a 2xx without the real page would add about 9,600 billed requests at this volume, and the total still fits inside the $99 plan. String chooses a path based on what a page needs, so production traffic mixes standard, premium, request, and browser rates. Decodo is cheaper than String when most String traffic needs a browser on a premium proxy. On premium fetches String is cheaper per usable page in this model, $1.00 against $1.39: the usage sits under the $99 Growth fee, which covers it, and any of it you do not use rolls over. String is cheaper still when most pages use its standard request path. Decodo's price advantage is real and should be measured alongside its 71.2% delivery rate.

Templates, formats, proxies, and MCP: Decodo wins

Decodo is a larger scraping toolbox. The Web Data API offers 100+ maintained target templates, sync and async jobs, structured parsers, browser actions, location and device controls, pagination, filtering, and multi-format responses. Raw proxy customers can choose residential, mobile, ISP, or datacenter pools instead of the managed API.

Its MCP server connects compatible agent clients to its scraping endpoints, with a hosted endpoint and an open-source repository. Markdown output keeps responses compact for LLM use. Decodo also lists n8n, LangChain, and OpenClaw integrations.

For procurement, Decodo publishes an ISO/IEC 27001:2022 certification covering its proxies and Scraping API, along with a Trust Center that exposes security, privacy, infrastructure, and data-processing materials. String's public product is more focused on retrieval than on a broad proxy and template catalog.

Which one should you pick?

Figures here come from the October 30, 2026 benchmark run and Decodo's pricing page, checked October 28, 2026.

  • Choose String when the core requirement is measured protected-page coverage. It returned at least one usable page on 100 of 100 targets; Decodo did so on 81.
  • Choose Decodo when premium-plus-JS pricing decides the purchase. Its $99 plan covers about 90,000 successful requests at $1.10 per 1,000.
  • Choose String when latency across failures matters. Its score was 4.24 seconds against 28.29. On the 51 sites both products returned in full, the median per-site time was 1.53 seconds for String and 23.38 for Decodo.
  • Choose Decodo for Yellow Pages, MarketWatch, or Barron's based on this run, where it passed five of five attempts to String's four, and test the exact URL before generalizing.
  • Choose Decodo when you also need 100+ templates, structured formats, raw proxy products, browser actions, MCP, or ISO 27001 documentation.
  • Test both with the open benchmark or a smaller target subset before committing spend.

Switching from Decodo to String

What carries over. A POST to data.decodo.com/v1/scrape, or to the legacy scraper-api.decodo.com/v2/scrape, becomes a POST to String's /v1/fetch with a bearer key. markdown: true maps to "format": "markdown", headless: "html" to "executeJS": true, and browser actions to String's actions. A move to Decodo's own new API also needs a new key, because the legacy token does not work there.

What you rebuild. The 100+ target templates and their parsers, async tasks and batches with callbacks, the crawl and map endpoints, and the residential, mobile, ISP, and datacenter proxy pools. String's /search endpoint and sitemap crawl cover search and URL discovery, and jsonSchema covers parsing for the fields you name.

Integrations to reconnect. Decodo publishes Python, TypeScript, and Go SDKs, a CLI, a hosted MCP server, and n8n and LangChain integrations. 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 Decodo today and run them through String. In this run Decodo returned nothing on 19 of the 100 sites, and String returned 18 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 17 web scraping APIs uses the same benchmark.

FAQ

Is Decodo better than String?

String was better on the measured fetch task: 98.6% (as of the October 2026 benchmark run) success against 71.2%, with a 4.24-second latency score against 28.29. Decodo is better on premium-plus-JS pricing and product breadth. In the October run it also beat String on four targets: Yellow Pages, MarketWatch, Barron's, and Kroger.

Is Decodo cheaper than String?

For pages that need a browser on a premium proxy, yes. Per Decodo's pricing page, checked October 28, 2026, its $99 (as of October 2026) plan prices premium proxies plus JavaScript at $1.10 per 1,000 and includes about 90,000 successes; String Growth is $99 a month, which includes $99 of usage, and bills that path at $3.25 per 1,000. At 100,000 calls, String's premium fetch costs $1.00 per 1,000 usable pages against Decodo's $1.39, and its standard fetch costs less.

Does Decodo charge for failed requests?

Not for its own failures. Decodo's billing docs say you pay only for successful requests, and its own 500, 524 and 613 failures are never charged. Its response-code table counts a 2xx or 4xx response as successful when a result comes back, so a block page with a body can bill. String does not bill a blocked request, but it bills a site's 404.

What Decodo configuration did the benchmark use?

The public adapter used the universal target with the premium proxy pool and headless: "html", which enables JavaScript rendering. It returned raw HTML and did not use a site-specific template or parser.

Does Decodo bypass Cloudflare?

More often than in the September run. Decodo passed 73.3% (as of the October 2026 benchmark run) of requests across 15 Cloudflare targets in October, up from 46.7%; String passed 98.7%. Decodo reached 68.0% on Akamai and 73.3% on AWS WAF.

Does Decodo have an MCP server?

Yes. Decodo documents an MCP server for compatible clients, backed by its scraping endpoints. It supports live scraping and structured outputs for agent workflows.

When should I use Decodo instead of String?

Use Decodo when you want premium-plus-JS scraping at a lower published rate, site-specific templates, multiple output formats, raw proxy options, browser actions, or ISO 27001 documentation. Use String when verified retrieval coverage and completion speed are the main job.

How can I verify the benchmark numbers?

Run the open-source benchmark with your own keys. The results JSON, target markers, and provider adapters are public. Start with your target subset because a full run makes thousands of billable calls.

Best Decodo Alternatives in 2026: 8 Tools ComparedUpdated November 11, 2026Best Web Scraping APIs 2026: 17 Compared by Success RateUpdated November 11, 2026Best Nimble Alternatives in 2026: 8 Tools ComparedUpdated November 11, 2026
Get your API key →Explore the Web Access API