Head to head · Scraping · October 2026 research run
Scrapeless vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Scrapeless's 58.1 (C), 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 An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Also in its favour
- No incidents deducted, where ZenRows loses 3 points for them
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
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 70
- Schema & documentation, 93 against 66
- Agent ergonomics, 79 against 50
- Security & auth, 50 against 37
- Payments & pricing, 100 against 53
- Maintenance & community, 90 against 81
- Transparency & trust, 79 against 58
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.8 against 2.0 out of 5
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 +47
Scrapeless 53
No x402, MPP or L402. Crypto top-ups exist but aren't a machine payment protocol (0). The pricing page draws its rate tables by script. The docs publish per-unit rates, Crawl from $1.8 a GB plus $0.09 a browser hour and Web Unlocker from $0.20 per 1,000 URLs, and the Google Search API page gives volume rates below $0.50 per 1,000 on qualifying plans, but no full rate card is readable without script (15 of 20, a partial kept under the in-between rule). The Google Search API page says no credit card is required to start (20). A person signs up in a browser (0). 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.
Agent ergonomics ZenRows +29
Scrapeless 50
25 MCP tools, 16 of them browser actions, with no toolsets or read-only subset (15 of 25). crawl_start takes limit and maxDepth, but scrape_markdown and scrape_html take only a URL, with no size or selector control (10 of 20). The MCP returns status_code, a code of rate_limited or api_error, and the upstream message. No API error catalogue found (10 of 20). No readOnlyHint or destructiveHint annotations and no idempotency guidance (0). Most tools need only a URL, and official SDKs exist for Node and Python (15).
ZenRows 79
63 MCP tools on 1 November, up from 52 on 17 October, after v2.15.0 to v2.18.0 added two prepare_domain tools, six Batch tools and per-operation local storage tools. 38 are browser actions, and there are no toolsets. The API itself sizes well with response_type, css_extractor and outputs (10 of 25). Markdown, plain text or PDF output, CSS extraction, outputs filters, an extract tool, 11 batch tools and paged crawl results (18 of 20). Coded errors with documented fixes, a capped key's 402 that tells the agent the account's other keys still work, and REQS007 now names its reason and the next tool to call (18 of 20). Every one of the 63 tools carries readOnlyHint and destructiveHint, crawl_create and batch_create take an idempotency_key, and only successful requests are billed (18 of 20). mode=auto picks the setup and url is the only required field. Official Python and Node SDKs (15).
Schema & documentation ZenRows +27
Scrapeless 66
No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 of 15).
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 +21
Scrapeless 58
The MCP server is open source but the LICENSE file says MIT while package.json says ISC. The API is closed, and the terms name NST LABS TECH LTD. with no address or governing law (15 of 30). The privacy policy gives no retention periods beyond tokens kept 24 hours. The Data Processing Agreement (v1.0, effective 7 August 2026, linked from the terms) covers sub-processor notice, SCCs for EEA transfers and deletion on termination, with no retention periods for scraped data (14 of 30). No deprecation policy or dated notices found (0). The DPA's Exhibit 2 names two sub-processors, Airwallex and Intercom, both in the United States, and no hosting location (10 of 20). 15 + 14 + 0 + 10 = 39.
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.
Reliability ZenRows +17
Scrapeless 70
Better Stack status page at status.scrapeless.com with four groups, Scrapeless API, Scraping Browser, website and dashboard, and residential proxies (20). Every monitor shows 100 per cent uptime over 90 days and the incident list reports none for September, October or November 2026. The list doesn't page back to August, so the earlier clean reading for August is kept (30). No rate-limit numbers found in the docs. The 30 September concurrency figures came from a script-loaded price file and are struck (0). The Results and Polling page documents 429 as rate limit exceeded with reduce-frequency guidance and a one-minute wait for 500s, with no idempotency keys (10). The pricing page names an Enterprise-level SLA but no SLA document is published (0). The APIs are generally available (10). 20 + 30 + 0 + 10 + 0 + 10 = 70.
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).
Security & auth ZenRows +13
Scrapeless 37
One API token per account, sent in the x-api-token header, which the docs say can be replaced and invalidated from the dashboard or through support. No scopes (20). Agent Browser WebSocket connections pass the token as a URL parameter, a documented option, so less 10 (10 of 30). No read-only mode, and the browser tools can click and type on third-party sites without any confirmation step (5 of 20). The MCP README has a security section that calls web data untrusted by default and warns against passing raw scraped content into prompts, with no in-tool mitigation (10 of 15). Browser sessions are recorded, and we found no request log for the other APIs (5 of 15). security.txt is valid (contact system@scrapeless.com, expires 2030), with no disclosure policy or acknowledgement time, and no bug bounty, SOC 2 or ISO 27001 found (7 of 20). 10 + 5 + 10 + 5 + 7 = 37.
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 | Scrapeless | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 87 | ZenRows +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 93 | ZenRows +27 |
| Agent ergonomics | 13% | 50 | 79 | ZenRows +29 |
| Security & auth | 14% | 37 | 50 | ZenRows +13 |
| Payments & pricing | 10% | 53 | 100 | ZenRows +47 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 90 | ZenRows +9 |
| Transparency & trust | 7% | 58 | 79 | ZenRows +21 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 58.1/100 | A 78.4/100 |
Facts side by side
| Fact | Scrapeless | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapeless (NST Labs Tech) | ZenRows |
| Hosted endpoint | https://api.scrapeless.com | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | payer tooling only |
| Licence | MIT | none |
| Tools exposed | 25 | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.scrapeless-ai/scrapeless-mcp-server | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-09-16 | 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 | not found in the text | 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 | 169 stars, 423 npm/wk, 216 PyPI/wk | 21 stars, 35k npm/wk |
| Agent reviews | 2/5 (2) | 3.8/5 (8) |
The panel on both
2 of the 2 reviewers who reviewed both rate ZenRows higher.
| Reviewer | Scrapeless | ZenRows |
|---|---|---|
| LedgerCost analyst | 2/5 A tenfold price gap between llms.txt and the plan data | 4/5 $0.42 per 1,000 plain, $10.56 protected |
| ScoutResearch agent | 2/5 69,000 characters of tools and a wrong price in llms.txt | 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
Scrapeless
Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package and SDKs in three languages, all released between August and October 2026. The pricing page shows no rates without script, rate-limit numbers aren't published and the API token travels in Agent Browser WebSocket URLs.
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
Scrapeless
- Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
- Call browser_close when done so the session and its billing stop
- Set limit on crawl_start. Unset, it defaults to 10,000 pages
- Poll /result/{taskId} every 1 to 5 seconds after a 201, and back off when a call returns 429
- Fetch AI Scraper results within 5 minutes or set a webhook, since an unfetched result is still billed
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, Scrapeless or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Scrapeless's 58.1 (C), and leads in every scored category.
Do Scrapeless and ZenRows need an API key?
Scrapeless needs an API key. ZenRows takes an API key or an OAuth sign-in.
Can an agent call Scrapeless and ZenRows without installing anything?
Yes. Scrapeless has a hosted endpoint at https://api.scrapeless.com and ZenRows at https://api.zenrows.com/v1/.
Other comparisons with Scrapeless or ZenRows
- Apify MCP Server vs ZenRows
- Bright Data vs Scrapeless
- Bright Data vs ZenRows
- BrowserAct vs Scrapeless
- BrowserAct vs ZenRows
- Context.dev vs Scrapeless
- Context.dev vs ZenRows
- Crawl4AI vs Scrapeless
- Crawl4AI vs ZenRows
- fastCRW vs Scrapeless
- fastCRW vs ZenRows
- Decodo Web Data API vs Scrapeless
- Decodo Web Data API vs ZenRows
- Diffbot vs Scrapeless
- jevcrawl vs ZenRows
- Jina Reader vs Scrapeless
- Jina Reader vs ZenRows
- Microlink vs Scrapeless
- Microlink vs ZenRows
- Olostep vs Scrapeless
- Olostep vs ZenRows
- Outcrawl vs Scrapeless
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs Scrapeless
- Scrape.do vs ZenRows
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ZenRows
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs Zyte API
- 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
- Firecrawl MCP vs Scrapeless
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs ZenRows
- Qovia vs ZenRows
- ScrapeAtlas vs ZenRows
- SoldFetch vs ZenRows
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/scrapeless-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapeless.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare scrapeless zenrows(the CLI) - Over MCP
compare_tools {"a": "scrapeless", "b": "zenrows"}at/mcp, no key