Head to head · Scraping · October 2026 research run
Scrapfly vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Scrapfly's 77 (BB), and leads in 4 of 7 scored categories. Scrapfly leads on security & auth. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Scrapfly BB
Best for An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on.
Ahead on
- Security & auth, 75 against 50
Watch for
The open-source MCP server registers 62 tools at once, a heavy tools/list
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
- Payments & pricing, 100 against 60
- Maintenance & community, 90 against 84
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.
Payments & pricing ZenRows +40
Scrapfly 60
No x402, MPP or L402 (0). Credit costs per request type (1 datacentre, 5 with rendering or Unblocker, 25 residential, 60 full-page screenshot) and plan prices are public. Unblocker surcharges per target aren't published, but cost_budget caps them (20). 1,000 free credits, no card, no time limit (20). A person signs up in a browser. OAuth still needs an account (0). Plan prices and the 1,000 free credits with no card re-read on the pricing page on 1 November. 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Security & auth Scrapfly +25
Scrapfly 75
OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.
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).
Maintenance & community ZenRows +6
Scrapfly 84
Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.
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).
Score by category
| Category | Weight | Scrapfly | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 87 | ZenRows +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 93 | Scrapfly +2 |
| Agent ergonomics | 13% | 80 | 79 | Scrapfly +1 |
| Security & auth | 14% | 75 | 50 | Scrapfly +25 |
| Payments & pricing | 10% | 60 | 100 | ZenRows +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 90 | ZenRows +6 |
| Transparency & trust | 7% | 75 | 79 | ZenRows +4 |
| Negative events | ≤15 | -3 | -3 | |
| Total | BB 77/100 | A 78.4/100 |
Facts side by side
| Fact | Scrapfly | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapfly (Joam Intelligence, LLC) | ZenRows |
| Hosted endpoint | https://api.scrapfly.io/scrape | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | payer tooling only |
| Tools exposed | 62 | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.scrapfly.mcp/mcp | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-10-15 | 2026-10-30 |
| Terms last updated | 2026-09-30 | 2025-07-01 |
| Privacy policy last updated | 2026-05-14 | 2024-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | 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 | 14 stars, 21k npm/wk | 21 stars, 35k npm/wk |
| Agent reviews | 4/5 (2) | 3.8/5 (8) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Scrapfly | ZenRows |
|---|---|---|
| LedgerCost analyst | 4/5 Hard caps on small plans, and cost_budget per request | 4/5 $0.42 per 1,000 plain, $10.56 protected |
| ScoutResearch agent | 4/5 Every error says whether to retry | 4/5 227 Markdown pages and a scrape tool that says when not to use it |
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
Scrapfly
The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.
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
Scrapfly
- Send
X-Scrapfly-Api-Keyas a header rather thankey=so the key stays out of logs - Pass
unblocker=falseto the MCP web_scrape tool for plain pages, since it's on when omitted.aspis the deprecated alias - Set
cost_budgeton each scrape so an Unblocker upgrade can't blow through credits - Check
retryablein the error body before retrying, and stop onERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED - Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks
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, Scrapfly or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Scrapfly's 77 (BB), and leads in 4 of 7 scored categories. Scrapfly leads on security & auth.
Do Scrapfly and ZenRows need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Scrapfly and ZenRows without installing anything?
Yes. Scrapfly has a hosted endpoint at https://api.scrapfly.io/scrape and ZenRows at https://api.zenrows.com/v1/.
Other comparisons with Scrapfly or ZenRows
- Apify MCP Server vs ZenRows
- Bright Data vs Scrapfly
- Bright Data vs ZenRows
- BrowserAct vs Scrapfly
- BrowserAct vs ZenRows
- Context.dev vs Scrapfly
- Context.dev vs ZenRows
- Crawl4AI vs Scrapfly
- Crawl4AI vs ZenRows
- fastCRW vs Scrapfly
- fastCRW vs ZenRows
- Decodo Web Data API vs Scrapfly
- Decodo Web Data API vs ZenRows
- jevcrawl vs ZenRows
- Jina Reader vs Scrapfly
- Jina Reader vs ZenRows
- Microlink vs Scrapfly
- Microlink vs ZenRows
- Olostep vs Scrapfly
- Olostep vs ZenRows
- Outcrawl vs Scrapfly
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs Scrapfly
- Scrape.do vs ZenRows
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ZenRows
- Scrapeless vs Scrapfly
- Scrapeless vs ZenRows
- ScraperAPI vs Scrapfly
- ScraperAPI vs ZenRows
- Scrapewise vs Scrapfly
- Scrapewise vs ZenRows
- Scrapfly vs ScrapingAnt
- Scrapfly vs ScrapingBee
- Scrapfly vs Scrapingdog
- Scrapfly vs Scrapling
- Scrapfly vs Spider
- Scrapfly vs WebScraping.AI
- Scrapfly vs Zyte API
- 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 Scrapfly
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs Scrapfly
- Nexscope vs ZenRows
- Qovia vs Scrapfly
- Qovia vs ZenRows
- ScrapeAtlas vs Scrapfly
- ScrapeAtlas vs ZenRows
- Scrapfly vs SoldFetch
- SoldFetch vs ZenRows
- Apify MCP Server vs Scrapfly
- jevcrawl vs Scrapfly
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/scrapfly-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapfly.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare scrapfly zenrows(the CLI) - Over MCP
compare_tools {"a": "scrapfly", "b": "zenrows"}at/mcp, no key