Are you an AI agent? To use String, read https://usestring.ai/agent-onboarding/SKILL.md first. 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 →
Web Access API

Access any page.
Even the hardest ones.

String is a web data API for developers and AI agents that fetches, searches and maps any public site without getting blocked. One HTTP call against any URL returns clean content, and you only pay when it comes back.

First request in seconds · Free to start · Pay only on success
Live · fetch
$ curl https://request.usestring.ai/v1/fetch \
  -H "Authorization: Bearer sk_live_…" \
  -d '{ "url": "https://www.zillow.com/homedetails/…" }'
200 · 412ms · 18.4 KB clean text
<!doctype html> … fully rendered, anti-bot cleared, no proxy to manage.

Fast

Warm browser pools and a rendering path that skips a cold spin-up wherever a target allows it. Concurrency holds the tail flat under load, so a burst of requests doesn't turn into a queue.

Reliable

It gets through the systems that others can't, and recovers on its own when a target shifts.

CloudflareDataDomePerimeterXAkamaiKasadaCAPTCHA challenges

Every request escalates automatically: lightweight request-based fetches, full browser rendering, premium proxies, geolocated routing, and CAPTCHA solving - which compliance-sensitive teams can switch off per request.

Who it's for

AI application companies

Give your agents live web data. In the September 16, 2026 benchmark, String got through more often and faster than Firecrawl and Browserbase.

Want your users to query live web data from inside your product? Connect the API or the MCP server.

GTM teams

Enrichment: Build agents that pull live web data for any deal or contact.

A Claygent-style research agent that doesn't get blocked.

Data companies

Quality: Reach pages you couldn't before because of anti-bot walls or engineering-capacity limits.

Stale data and coverage gaps turn into customer tickets.

Vibe coders

Ship without a scraping stack: point a script at any page and get clean data back, no proxies, retries, or bot walls to babysit.

Building a side project or an agent on a weekend? Pull the pages you need with a single call instead of losing Saturday to rotating proxies and a Cloudflare challenge that wasn't there yesterday.

Q3 2026 · re-run monthly

The Web Data Frontier Benchmark, in full

Every provider ran against every target at the same time. Two numbers decide whether a scraper is worth running: did it get through, and how fast.

100 hard targetsAll 17 tested providers500 requests per providerData generated October 30, 2026View the open-source benchmark on GitHub ↗
The full benchmark, always current →Why we built our own benchmark →
Benchmark methodology
Real pages, real defenses, verified content

We tested String Web Access API against fifteen other web access APIs by loading 100 real-world pages known to be difficult to scrape, including targets protected by anti-bot and WAF systems such as DataDome, Akamai, Cloudflare, and Kasada.

The suite covers pages with high scraping value: product detail pages, search results, social platforms, and similarly protected surfaces. Each URL was requested 5 times per provider - 500 requests each - and a request only counted as successful when the API returned a 2xx and the response contained the page's expected content.

Latency includes every target. Content uses the 75th percentile of successful attempt latencies. A complete miss uses the 75th percentile of providers that returned content for that target, or the 90-second timeout when nobody succeeds.

01 · Overall success rate
All targets, all requests. Higher is better.
string
98.6%
scrapedo
94.0%
context_dev
93.0%
scrapfly
86.8%
scrapingbee
85.2%
firecrawl
81.2%
zyte
79.6%
apify
79.4%
scraperapi
76.4%
bright
75.4%
decodo
71.2%
nimble
68.0%
oxylabs
67.4%
browserbase
43.0%
zenrows
41.8%
scrapingant
40.0%
scrapingdog
27.6%
0%25%50%75%100%
02 · Latency score
Mean per-target p75 latency. Lower is better.
string
4.24s
scrapedo
5.08s
context_dev
10.96s
scrapfly
19.62s
scrapingbee
20.30s
firecrawl
8.87s
zyte
14.43s
apify
24.87s
scraperapi
15.19s
bright
27.88s
decodo
28.29s
nimble
22.65s
oxylabs
16.62s
browserbase
18.01s
zenrows
21.91s
scrapingant
18.39s
scrapingdog
31.52s
0s9s18s27s36s
Get an API key ↗Free to start · Pay only on success
Data generated October 30, 2026 (Q4 2026 run)

One call. That's the integration.

Send a URL, get clean content back. No proxy list to rotate, no headless browser to babysit.

Request · curl
curl https://request.usestring.ai/v1/fetch \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://hard-target.com", "format": "markdown" }'
200 · 412ms · 18.4 KB clean text

Give your agents the same reach

Add String over MCP and your agent fetches any page, even the hardest ones, as a single tool call, in Claude, ChatGPT, Cursor, Perplexity, or anything that speaks the protocol.

Already on Apify? The same engine ships as 30 ready-to-run Actors on the Apify Store. See the list.

MCP · mcp.json
{
  "mcpServers": {
    "string-web-access": {
      "type": "http",
      "url": "https://mcp.usestring.ai?login"
    }
  }
}

Frequently asked questions

What is the Web Access API?

A web scraping API for humans and agents. One HTTP call against any URL returns the page as clean content, fully rendered and past whatever anti-bot is sitting in front of it. You only pay when it comes back.

Which anti-bot systems does it get through?

Cloudflare, DataDome, PerimeterX, Akamai, Kasada, and CAPTCHA challenges. Every request escalates on its own: a lightweight fetch first, then full browser rendering, premium proxies, and geolocated routing if the target needs it. CAPTCHA solving is part of the same escalation, and teams with compliance constraints can turn it off per request.

How fast is it?

Browser pools stay warm and the rendering path skips a cold spin-up wherever a target allows it, so a burst of requests doesn't turn into a queue.

How reliable is it?

As of October 2026, String passed 98.6% of requests in the open-source Web Data Frontier Benchmark (https://usestring.ai/benchmark), the best success rate of any provider in the October 2026 run. The run covers 100 hard targets at 500 requests per provider, and repeats monthly.

How many requests can I run at once?

Up to 10,000 fetches and 5,000 browser sessions at once, on every plan. The request rate is what grows with your plan, and higher rates are available on request.

Can my agent use it?

Yes. Add String over MCP and your agent fetches any page as a single tool call, in Claude, ChatGPT, Cursor, Perplexity, or anything that speaks the protocol.

How much does it cost?

Start with 20,000 free standard fetches, no card needed. After that, plans start at $19/month, and the fee comes back as usage credit billed per request. Blocked requests cost nothing. Prices as of October 2026, from the String pricing page (https://usestring.ai/pricing).

Get your API key now

Get an API key ↗
First request in seconds · Free to start · Pay only on success