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 Nimble (2026): 100 protected sites

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

Which is better, String or Nimble?

String is a fetch API for teams whose target pages sit behind bot protection. It returns each page as the site serves it. 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 Nimble returned 68.0%, down 0.6 points from the September run. String's failure-aware latency score was 4.24 seconds against Nimble's 22.65. The October run, like September's, called Nimble with render: "auto", which hands each request to Nimble's own escalation engine; the August run had rendering off.

  • Choose String if protected-page coverage decides it. String returned 98.6% of requests and Nimble 68.0%, and a usable page on 100 of 100 sites to Nimble's 78, in the October 30, 2026 run.
  • Choose Nimble if you need search agents, extraction templates, crawling, batches, residential proxies, or its published SOC 2 Type II controls.
  • Do not switch if Nimble already returns your pages and premium-path cost decides it. Extract costs $1 per 1,000 successful URLs (as of October 2026).

TL;DR

  • Success rate in the October 30, 2026 run: String 98.6% (493/500), Nimble 68.0% (340/500)
  • Latency score: String 4.24s (first of 17), Nimble 22.65s (13th of 17)
  • Perfect targets: String 95 of 100, Nimble 56. Total shutouts: String 0, Nimble 22
  • Nimble's clean wins: Yellow Pages, MarketWatch, and Barron's, each 5/5 against String's 4/5, and Kroger, 5/5 against String's 2/5
  • Price: Nimble's current Extract API is $1 per 1,000 successful URLs with no commitment
  • Method caveat: the benchmark used v1 with render: "auto", while new integrations should use v2
  • Every benchmark number comes from a public harness you can run with your own keys
String Nimble
Product type Fetch, search, sitemap, and remote browser Extract, search, map, crawl, agents, templates, media, and proxies
Benchmark success rate 98.6% (493/500) 68.0% (340/500)
Latency score 4.24s, first of 17 22.65s, 13th of 17
Per-target outcome 95 perfect, 5 partial, 0 zero 56 perfect, 22 partial, 22 zero
Anti-bot highlights 100% AWS WAF, Kasada, Fastly and sites with no named vendor 100% Fastly, 86.7% Kasada, 82.2% PerimeterX, 81.5% on sites with no named vendor
Pricing basis Plan plus successful-request usage; credits roll over $1 per 1,000 successful Extract URLs, no commitment
Free evaluation First 20,000 standard fetches 5,000 free pages, no card required
Agent tooling Hosted MCP and HTTP API Hosted MCP, Web Search Agents, CLI, Python, Node, and Go SDKs
Where it wins Measured protected-page coverage and latency Four targets, flat extraction price, product breadth, enterprise controls

How we tested, and why Nimble's adapter needs another run

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, provider adapters, and 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 Nimble adapter called POST https://sdk.nimbleway.com/v1/extract with the URL and render: "auto", which lets Nimble's own engine choose rendering and driver. Before the September run it sent render: false, raw HTML over a residential Nimble IP with no headless browser; the harness changed it in pull request 16.

One qualification remains. Nimble's current v2 introduction says new integrations should target v2, and the current Extract API supports auto, VX6, VX8, VX10, VX12, Pro variants, JavaScript rendering, and browser actions. The October run still called v1, so a v2 rerun could score differently. Until that run exists, this page reports the measured result and refuses to present it as Nimble's product ceiling.

The harness is open to a corrected adapter. A Firecrawl engineer used that route in benchmark pull request 6; the next run improved Firecrawl's result by 7.7 points. Nimble can do the same.

Pricing and product claims were checked against live first-party pages on August 31, 2026. Performance figures are from the October 30, 2026 run.

What Nimble is

Nimble's current platform is much broader than the endpoint the benchmark tested. The v2 API includes URL extraction, web search, Web Search Agents, extraction templates, mapping, crawling, SERP retrieval, media downloads, scheduled jobs, and async task and batch APIs. Its Web API combines Nimble's browser drivers with its residential proxy network and can deliver raw or structured data.

The Extract endpoint can return HTML and Markdown, parse structured output, choose a driver, render JavaScript, run browser actions, set location and device parameters, capture network traffic, and manage sessions. Current docs list a default 83 queries per second for the VX driver family.

Nimble also ships a hosted MCP server with tools for search, extract, map, crawl, extraction templates, and research agents. String is narrower: one fetch endpoint with automatic escalation, plus search, sitemap crawling, a remote browser over CDP, and MCP.

The same request in Nimble 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 -X POST https://sdk.nimbleway.com/v2/extract \
  -H "Authorization: Bearer $NIMBLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.example.com/product/123", "render": true, "driver": "vx10", "formats": ["markdown"]}'
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"}'

Nimble's Extract endpoint replaced its Web API and moved from Basic to bearer auth. It defaults to the vx6 HTTP driver with no JavaScript. Rendering needs render: true on the vx8 or vx10 driver, and vx10 is the stealth driver. formats: ["markdown"] returns markdown. 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%, Nimble 68.0%

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
Firecrawl 406/500 81.2% 8.87s
Bright Data 377/500 75.4% 27.88s
Nimble 340/500 68.0% 22.65s
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

Nimble ranked 12th of 17 for success and 13th 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.

Again, those ranks belong to Nimble's v1 Extract endpoint with render: "auto". They do not answer what v2 with a chosen rendered VX driver would have done.

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

Nimble passed Yellow Pages, MarketWatch, Barron's, and Kroger on all five attempts. String passed the first three four times each and Kroger twice. They were the only four targets where Nimble beat String outright. AutoTrader and Allegro, its two wins in September, went the other way: AutoTrader was 5/5 for String and 1/5 for Nimble, and Allegro 5/5 for both.

The industry view has other strengths. Nimble reached 100% in grocery and food, ahead of String's 88%, 100% in gaming, 95.0% across social platforms, and 86.7% in both news and finance and developer and research. Against named anti-bot systems, it posted 100% on the single Fastly target, level with String, 86.7% on Kasada, and 82.2% on PerimeterX.

Those results are the reason to read the category table rather than the headline. Nimble leads String on grocery, is close on social platforms, and is far behind on retail at 47.1%, reviews and local at 50.0%, and tickets and events at 25.0%. Teams targeting the first group should test Nimble directly. These category and anti-bot figures come from the October 30, 2026 benchmark run.

The measured coverage gap is 22 rescued targets

Outcome across 100 sites String Nimble
Passed all 5 attempts 95 56
Passed 1 to 4 attempts 5 22
Passed none 0 22

Nimble returned nothing on 22 sites: Temu, Mouser, Trustpilot, Best Buy, Crunchbase, Apartments.com, Lowe's, Skyscanner, Home Depot, AutoZone, Louis Vuitton, Saks Fifth Avenue, StubHub, Ticketmaster, StockX, Zara, American Airlines, Monster, Reuters, eMAG, CarGurus and AXS. String passed 21 of the 22 on all five attempts and Skyscanner four times.

The anti-bot columns show the same shape. Nimble passed 68.0% (as of the October 2026 benchmark run) of Cloudflare requests against String's 98.7%, 51.0% of Akamai against 97.0%, and 64.2% of DataDome against 97.9%. Its Cloudflare result has risen in each run since August: 34.7% in August, 62.7% in September, and 68.0% in October. Its strongest multi-site named wall is Kasada at 86.7%, against String's 100%.

Pricing: Nimble wins when String needs premium fetches

Nimble's current API pricing charges $1 per 1,000 successful Extraction Tool URLs, with no commitment. Only successful requests bill. The free trial includes 5,000 pages with no card. Search costs $1.10 per 1,000 lite inputs or $5 per 1,000 fast inputs. Web Search Agents range from $0.025 to $2 per task by effort. Residential proxy traffic is $5.30 per GB.

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 (as of October 2026), which includes $99 of usage at $0.16 or $0.90. Usage above the included amount bills at the same rates. Blocks are free and unused credit rolls over.

At 100,000 calls against the benchmark target mix, the cheapest published String plan for each path gives this model:

Assumption Monthly cost Cost per 1,000 usable pages
Nimble Extract 68,000 successful URLs at $1/1k; failures free $68.00 $1.00
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. String chooses a path based on what a page needs, so production traffic mixes rates. Nimble's current price page lists one $1 extraction rate rather than a separate rendered surcharge. On the premium path the two are close: String's usage sits under the $99 Growth fee, which covers it, and any of it you do not use rolls over. That puts String at $1.00 per 1,000 usable pages, level with Nimble's $1.00, while Nimble's monthly bill is lower. String is cheaper when most requests use its standard path. Both vendors exclude failed requests from billing, so retries do not create the same cost penalty as call-based competitors.

Product breadth and enterprise controls: Nimble wins

Nimble's advantage grows outside one-page fetches. Its Search API can retrieve and summarize results with domain, date, locale, and focus controls. Map discovers a site's URLs. Crawl retrieves multiple pages asynchronously. Extract Templates add reusable structured parsers, and Web Search Agents run longer cited research tasks. The platform offers batch and async extraction plus its own residential proxy API.

For agent clients, Nimble's hosted MCP server exposes that surface through Streamable HTTP. It also offers a CLI and Python, Node, and Go SDKs. String's MCP is centered on fetch, search, and sitemap tools.

Nimble also publishes a stronger enterprise-control page. Its compliance documentation states SOC 2 Type II, zero data retention, GDPR and CCPA coverage, standard contractual clauses, encryption, RBAC, and audit trails. Choose Nimble when those controls and the surrounding data platform outweigh the measured fetch gap.

Which one should you pick?

  • Choose String when the core requirement is measured protected-page coverage. It returned at least one usable page on 100 of 100 targets; Nimble did so on 78.
  • Choose Nimble when premium-path economics decide the purchase. Current Extract pricing is $1 per 1,000 successful URLs with no base commitment.
  • Choose String when latency across failures matters. Its score was 4.24 seconds against 22.65. On the 52 sites both returned in full, the median per-site time was 1.50 seconds for String and 12.11 for Nimble.
  • Choose Nimble when the workload also needs search agents, templates, mapping, crawling, batches, residential proxies, or published enterprise controls.
  • If you are evaluating current Nimble, do not copy the benchmark adapter unchanged. Test v2 with an appropriate rendered or automatic driver, then compare the result with String on your own URLs.
  • Re-run the open benchmark or a smaller target subset before committing spend. The figures above come from the October 30, 2026 run and Nimble's pricing page, checked in August 2026.

Switching from Nimble to String

What carries over. A POST to sdk.nimbleway.com/v2/extract, or to the legacy api.webit.live Web API, becomes a POST to String's /v1/fetch with a bearer key. formats: ["markdown"] maps to "format": "markdown", render: true to "executeJS": true, and browser actions to String's actions. The driver choice goes away, because String picks the fetch path.

What you rebuild. Extract Templates and scheduled Extract Jobs, async and batch extraction with callbacks, Search, Map, Crawl, agent research runs, file parsing, and the residential proxy gateway. String's /search endpoint and sitemap crawl cover search and URL discovery. Templates become jsonSchema extraction or your own parser.

Integrations to reconnect. Nimble publishes Python, Node, and Go SDKs, a CLI, a hosted MCP server, plugins for coding agents, and integrations for LangChain, LlamaIndex, the Vercel AI SDK, Databricks, and Snowflake. Its docs list no n8n, Zapier, or Make integration. 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 Nimble today and run them through String. In this run Nimble returned nothing on 22 of the 100 sites, and String returned 21 of those on every attempt. Test Nimble's current Extract endpoint with a rendering driver beside it, compare pages returned and cost per usable page, and move only the targets that improve. Leave custom headers off for the test: String does not bill a blocked request unless that request sent custom headers. The first 20,000 String standard fetches are free with no card. If Nimble is one option among several, the Nimble alternatives comparison ranks the substitutes on the same benchmark.

FAQ

Is Nimble better than String?

String was better on the measured fetch task: 98.6% (as of the October 2026 benchmark run) success against 68.0%, with 0 total shutouts against 22 and a faster failure-aware latency score. Nimble is broader, level with String's premium fetch path per usable page at the volume modeled above, ahead of String on grocery, and close to String on social platforms.

Is Nimble cheaper than String?

Nimble Extract is $1 per 1,000 successful URLs with no commitment. String Starter is $19 a month (as of October 2026), which includes $19 of usage at $0.25 per 1,000 standard fetches; Growth is $99 a month, which includes $99 of usage at $0.90 per 1,000 premium fetches. String is cheaper for mostly standard traffic. On mostly premium traffic the two are level per usable page: at 100,000 calls both work out to $1.00 per 1,000, and above about 100,400 calls a month String comes in lower, falling toward its $0.90 rate. Nimble's monthly bill stays lower because it bills fewer successful pages.

Does Nimble charge for failed requests?

No. Nimble's pricing page says only successful API requests are charged. String also bills only requests that return content.

What Nimble configuration did the benchmark use?

The public adapter called legacy POST /v1/extract with render: "auto", which lets Nimble's engine choose rendering and driver. It did not use v2 Extract, browser actions, or a fixed driver choice. The August run sent render: false.

Does Nimble bypass Cloudflare?

Sometimes. It passed 68.0% (as of the October 2026 benchmark run) of requests across 15 Cloudflare targets, while String passed 98.7%. The run used v1 with render: "auto"; v2 with a chosen rendered driver was not tested.

Does Nimble have an MCP server?

Yes. Its hosted MCP server exposes search, extract, map, crawl, templates, and Web Search Agent operations to compatible clients through Streamable HTTP.

When should I use Nimble instead of String?

Use Nimble when you need one web-data platform for extraction, search, research agents, maps, crawls, templates, proxies, and enterprise controls, or when its flat $1 (as of October 2026) successful-extract rate beats your String path mix. Use String when verified page retrieval is the main job. The $1 rate is from Nimble's pricing page.

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. For Nimble, update the adapter to v2 and choose the driver configuration you actually plan to buy.

Best Zillow Scrapers 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