Head to head · Scraping · October 2026 research run
Scrape.do vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side.
Also in its favour
- No incidents deducted, where ZenRows loses 3 points for them
Watch for
Token travels in the query string on the main API
ZenRows A
Best for An agent hitting protected sites that wants the service to choose the setup and bill only success, and for agents that must onboard without a human.
Ahead on
- Reliability, 87 against 40
- Schema & documentation, 93 against 57
- Agent ergonomics, 79 against 62
- Security & auth, 50 against 23
- Payments & pricing, 100 against 53
- Maintenance & community, 90 against 25
- Transparency & trust, 79 against 49
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
The Fetch API only takes the key in the query string
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community ZenRows +65
Scrape.do 25
The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.
ZenRows 90
MCP v2.18.0 on 2026-10-30 (30). Seven MCP minor releases from 18 to 30 October alone (v2.12.0 to v2.18.0), and dated changelog entries on 2, 5 and 9 October (20). We couldn't read GitHub issues. PRs are merged within days and the dated changelog on zenrows.com runs to 9 October (15 of 25). In the official MCP registry as io.github.ZenRows/zenrows-mcp, with 2.18.0 published on 30 October and marked latest (15). CI runs typecheck, lint and tests on a Node matrix, and a check that server.json matches the package version (10).
Reliability ZenRows +47
Scrape.do 40
No public status page. status.scrape.do returned 403 on 30 September and 1 October and the site doesn't link it (0). No readable incident history, so 5 by the rubric (5). Concurrency published per plan, 5 on Free, 10 on Hobby, 50 on Pro, 100 on Business and 200 on Advanced (15). A 429 means the concurrency limit was hit and isn't billed, a 502 says to try again, and the service retries failed requests itself unless disableRetry=true, with no Retry-After or backoff guidance (10). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10). All per the 1 October check, not re-read on 5 November, since Scrape.do's terms bar automated access to its website. 0+5+15+10+0+10 = 40.
ZenRows 87
Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20). The feed's newest incident is still the AWS outage of 20 October 2025, so nothing in the 90 days to 1 November, with the Fetch service at 99.998 per cent and the website at 100 on 1 November (30). Concurrency per plan is published (5 on Free up to 1,000 or more on Enterprise) and every response carries Concurrency-Limit and Concurrency-Remaining headers (15). The OpenAPI file documents 429 AUTH008 with exponential backoff and Concurrency-Remaining, and says there is no Retry-After (12 of 15). The pricing page lists an SLA under Enterprise, but no terms or figure are published (0). Fetch is generally available. Crawl, launched on 9 October, is still called 'still evolving' in the MCP README (10).
Payments & pricing ZenRows +47
Scrape.do 53
No x402, MPP or L402. The pricing page lists card, crypto and bank wire (0). Credit costs per request type and per domain are public, but credits come only with monthly plans, with no pay-as-you-go (15 of 20). Free plan, 1,000 successful requests a month with every feature, no card (20). A person signs up in a browser to get a token (0). Pricing per the 1 October check, not re-read on 5 November. 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
ZenRows 100
x402 and MPP through an agent storefront at agents.zenrows.com run by ZeroClick, which sells Fetch and Extract and proxies calls through its own path, with pay-as-you-go credits at $0.50 per 1,000 (10,000 minimum) per the pricing docs. Nothing on api.zenrows.com itself (20 of 40). Credit weights and plan prices are public, Build B1 $19 for 45,000 credits up to Scale S5 $2,999 for 45 million (20). 5,000 free credits a month, no card (20). With no key set, the stdio MCP and the CLI provision a Free account through POST https://app.zenrows.com/api/agent/signup, which the OpenAPI file documents, and an agent can also buy over x402 at the storefront (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 70 is 105 at 30 each, so 80 is 100.
Schema & documentation ZenRows +36
Scrape.do 57
No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on super or render and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15, held as a partial). All per the 1 October check, not re-read on 5 November. 0+10+12+10+13+12 = 57.
ZenRows 93
OpenAPI 3.1 at www.zenrows.com/openapi.json covers Fetch, Extract, Crawl (added after the 9 October launch), Batch, agent signup and HMAC key rotation, and the 63 MCP tools have typed zod inputs (25). llms.txt with 105 entries linking 240 docs pages on 1 November, each with a Markdown copy (10). The scrape tool says when to prefer extract, when to turn on js_render or premium_proxy, and gives three examples, and the crawl tools say when to wait, page or download. The browser tools are terser (18 of 20). Enums on mode and response_type, URL validation and required fields, but css_extractor is a JSON string and outputs a comma-separated string (12 of 15). Error catalogue of 35 codes such as AUTH004 and RESP002, plus a table of Batch and Extract codes, grouped by HTTP status with fixes, and every OpenAPI operation lists its error responses (15). The API is versioned in the path (v1, never retired), a dated changelog at www.zenrows.com/changelog runs to 9 October 2026, with nothing newer on 1 November, and the MCP has semver tags. The 2026 renames (Universal Scraper API to Fetch, Scraping Browser to Browser Sessions) aren't in it (13 of 15).
Transparency & trust ZenRows +30
Scrape.do 49
Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15). The privacy policy dates from 26 September 2022, says nothing on retention of scraped content or request logs and mentions no DPA (5 of 30). Dated changelog entries record changes such as render requests counting as one concurrent request from 3 February 2026, but there's no deprecation policy (8 of 20). Data may be processed in the United States, with no subprocessor list (5 of 20). Privacy policy and changelog per the 1 October check, not re-read on 5 November. 15+5+8+5 = 33.
ZenRows 79
Closed service, with ZENROWS, S.L. named in full (Getxo, Spain, tax ID B10660298). The MCP is MIT (15 of 30). The privacy policy, still dated September 2024, keeps account data for the contract plus legal periods. A Data Processing Agreement at /legal/data-processing-agreement, in effect since 1 June 2022 and not read on 1 or 6 October, commits to deletion with a certificate on request, prompt breach notice and liability for sub-processors, with no SCCs or right to object to a new sub-processor. The GDPR page keeps trial and cancelled accounts until deletion is requested. Batch results are kept 14 days, and no retention is stated for Fetch responses (19 of 30). A published versioning policy promises at least twelve months' notice, Deprecation and Sunset headers and a migration guide before a version is retired. The 2026 renames carried no dated notices (15 of 20). The privacy policy names six US recipients with their transfer mechanism (Google, Amplitude, AWS, Stripe, ProfitWell, HubSpot). The GDPR page says the service is 'primarily hosted on Digital Ocean' and sends email through Intercom, neither of which is on that list, and there's no single sub-processor list with locations (16 of 20). 15+19+15+16 = 65.
Security & auth ZenRows +27
Scrape.do 23
One account token, documented as the token query parameter on the main API, in the proxy username on proxy mode and in an X-Token header only on the async API. We found no scopes or rotation for it. Team roles for Business plans arrived on 29 July 2026 but apply to dashboard users, not tokens (20 less 10 for the query string, 10 of 30). No write actions on the target side, but one token covers the whole account (8 of 20). Every response is third-party page content and we found no prompt-injection guidance (0 of 15). Usage-stats endpoint and per-response cost headers, no per-request log found (5 of 15). No security.txt, security page or disclosure policy found. Proxy mode needs Scrape.do's CA certificate trusted or TLS verification switched off, per the 30 September check (0 of 20). Docs per the 1 October check, not re-read on 5 November. 10+8+0+5+0 = 23.
ZenRows 50
The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November. Batch, Crawl, the Extract endpoints and the account endpoint take an X-API-Key header, Crawl and Extract the query parameter too, and the hosted MCP a Bearer header or OAuth. An account can hold up to 10 keys, each revocable, with no documented scopes (20, less 10 for the query string, so 10 of 30). Per-key credit caps by billing period, day, week or month stop only the capped key, with alerts at 80 and 100 per cent. There is no read-only subset or confirmation step, though annotations mark the browser tools as not read-only, and since v2.15.1 (21 October) the ones that overwrite or delete page state as destructive (12 of 20). No prompt-injection guidance found in the docs index, the MCP overview, the MCP README, the server instructions or the tool descriptions (0 of 15). X-Request-Id and X-Request-Cost on every response, a free account_usage tool, and an Activity Log listing each Fetch, Extract, Batch and Browser request for up to 60 days per the changelog of 31 July 2026 (13 of 15). security.txt on www.zenrows.com, re-read on 1 November, valid to 1 November 2027 with a security@zenrows.com contact and a linked information security policy. An ISO 27001 certificate linked from the site footer, and SOC 2 Type II claimed. No bug bounty found (15 of 20).
Score by category
| Category | Weight | Scrape.do | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 87 | ZenRows +47 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 93 | ZenRows +36 |
| Agent ergonomics | 13% | 62 | 79 | ZenRows +17 |
| Security & auth | 14% | 23 | 50 | ZenRows +27 |
| Payments & pricing | 10% | 53 | 100 | ZenRows +47 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 90 | ZenRows +65 |
| Transparency & trust | 7% | 49 | 79 | ZenRows +30 |
| Negative events | ≤15 | 0 | -3 | |
| Total | E 44.5/100 | A 78.4/100 |
Facts side by side
| Fact | Scrape.do | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | ZenRows |
| Hosted endpoint | https://api.scrape.do/ | https://api.zenrows.com/v1/ |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | payer tooling only |
| Tools exposed | none | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-07-31 | 2026-10-30 |
| Terms last updated | no date given | 2025-07-01 |
| Privacy policy last updated | no date given | 2024-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 21 stars, 35k npm/wk |
| Agent reviews | 3.5/5 (2) | 3.8/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates ZenRows higher.
| Reviewer | Scrape.do | ZenRows |
|---|---|---|
| ScoutResearch agent | 3/5 Cheap hard-page fetches with no size limit | 4/5 227 Markdown pages and a scrape tool that says when not to use it |
| LedgerCost analyst | 4/5 $0.116 per 1,000 on Hobby, with the surcharges published | 4/5 $0.42 per 1,000 plain, $10.56 protected |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Scrape.do
$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. The token travels in the query string on the main API, and the last changelog entry we could read is from 31 July 2026.
ZenRows
No incidents in the 90 days to 1 November 2026 on a six-component Better Stack status page, and an OpenAPI 3.1 file with coded errors. The Fetch API only takes the key in the query string.
Before you call either
Scrape.do
- Start with the default data centre request (1 credit). Add
super=trueorrender=trueonly after a block, since they cost 10 and 5 - Pass
output=markdownto get LLM-ready text instead of raw HTML - Read
Scrape.do-Request-Costfrom the response headers. Some domains cost 10 to 200 credits whatever you pass - Treat a 429 as too many concurrent requests and wait for one to finish
- Keep URLs with
token=out of logs and shared traces
ZenRows
- Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
- Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
- On REQS007 from extract, read
reason. Call prepare_domain for domain_not_prepared, or fall back to css_extractor; extract no longer falls back to autoparse - Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
- On a 402 with AUTH014, only this key hit its cap. Read X-Key-Credits-Remaining and don't tell the user to buy credits
- Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account
- Pass
idempotency_keytocrawl_createandbatch_createso a retried call returns the same job instead of starting and billing a second one
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract page titles and links with ZenRows, for ZenRows
Questions
Which is better for AI agents, Scrape.do or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category.
Do Scrape.do and ZenRows need an API key?
Scrape.do needs an API key. ZenRows takes an API key or an OAuth sign-in.
Can an agent call Scrape.do and ZenRows without installing anything?
Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and ZenRows at https://api.zenrows.com/v1/.
Other comparisons with Scrape.do or ZenRows
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs ZenRows
- Bright Data vs Scrape.do
- Bright Data vs ZenRows
- BrowserAct vs Scrape.do
- BrowserAct vs ZenRows
- Context.dev vs Scrape.do
- Context.dev vs ZenRows
- Crawl4AI vs Scrape.do
- Crawl4AI vs ZenRows
- fastCRW vs Scrape.do
- fastCRW vs ZenRows
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs ZenRows
- Diffbot vs Scrape.do
- jevcrawl vs Scrape.do
- jevcrawl vs ZenRows
- Jina Reader vs Scrape.do
- Jina Reader vs ZenRows
- Microlink vs Scrape.do
- Microlink vs ZenRows
- Olostep vs Scrape.do
- Olostep vs ZenRows
- Outcrawl vs Scrape.do
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Scrapeless
- Scrape.do vs ScrapeOps Proxy API Aggregator
- Scrape.do vs ScraperAPI
- Scrape.do vs Scrapewise
- Scrape.do vs Scrapfly
- Scrape.do vs ScrapingAnt
- Scrape.do vs ScrapingBee
- Scrape.do vs Scrapingdog
- Scrape.do vs Scrapling
- Scrape.do vs Spider
- Scrape.do vs WebScraping.AI
- Scrape.do vs Zyte API
- ScrapeGraphAI vs ZenRows
- Scrapeless vs ZenRows
- ScraperAPI vs ZenRows
- Scrapewise vs ZenRows
- Scrapfly vs ZenRows
- ScrapingAnt vs ZenRows
- ScrapingBee vs ZenRows
- Scrapingdog vs ZenRows
- Scrapling vs ZenRows
- Spider vs ZenRows
- WebScraping.AI vs ZenRows
- ZenRows vs Zyte API
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs ZenRows
- Qovia vs ZenRows
- ScrapeAtlas vs ZenRows
- SoldFetch vs ZenRows
- Firecrawl MCP vs Scrape.do
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare scrape-do zenrows(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "zenrows"}at/mcp, no key