Head to head · Scraping · October 2026 research run
Spider vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Spider's 74.3 (BB), and leads in every scored category. Both do scraping. Spider accepts x402. ZenRows doesn't.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Spider BB
Best for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Also in its favour
- An agent can pay per call over x402, with no account
- Open source
- No incidents deducted, where ZenRows loses 3 points for them
Watch for
No security.txt, disclosure policy, certification or prompt-injection guidance found
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
- Schema & documentation, 93 against 87
- Agent ergonomics, 79 against 70
- Security & auth, 50 against 42
- Payments & pricing, 100 against 94
- Maintenance & community, 90 against 75
- Transparency & trust, 79 against 70
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.8 against 3.3 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.
Maintenance & community ZenRows +15
Spider 75
The newest dated change is the unblocker's removal from the hosted MCP and the client sources on 1 October 2026, 31 days before 1 November, and the product changelog's newest entry is still 10 September (provider router), so within 90 days but not 30 (20, cause time, 30 on 17 October). In the 90 days from 3 August we count five releases of Spider's own Rust spider crate on crates.io (2.53.5 on 17 August, 2.53.6 on 18 August, 2.53.7 on 1 September, 2.53.8 on 3 September and 2.53.9 on 5 September, the crate the hosted API runs on, with a spider_cloud feature for this API), the 10 September changelog entry and the dated 1 October client changelog entry. The @spider-cloud/spider-client 0.2.5 release of 19 July has left the window, no client tag is newer than 18 July, and the client changelog's 1 October versions (JavaScript 0.3.0, Python 0.2.0) have no release tags in the repository on 1 November. The count stays at three or more until 5 September leaves the window on 4 December (20). We couldn't read GitHub issues. Dated changelog and support by email (12 of 25). In the official MCP registry as cloud.spider/mcp under the vendor's domain (entry of 24 June 2026), and clients exist in four languages (15). The clients repo runs CI for Node, Python and Rust. The MCP repo has no CI (8 of 10). 20 + 20 + 12 + 15 + 8 = 75.
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).
Agent ergonomics ZenRows +9
Spider 70
21 tools on the hosted MCP (7 core, 5 AI, 9 browser) since the unblocker tool was dropped, and 12 in the stdio package on its main branch, with no toolsets (15 of 25). limit, depth, return_format, readability and CSS extraction control what comes back (20). Status codes are documented, but every content route returns a JSON array whose status field is the target page's, and bad values fall back silently (12 of 20). No tool annotations, and llms.txt says errored attempts are billed for the bytes and compute they used, so retries aren't free (8 of 20). request defaults to smart and only url is required. Official clients in Python, JavaScript, Rust and Go plus a CLI (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).
Transparency & trust ZenRows +9
Spider 70
The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.
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 +8
Spider 42
Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42.
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).
Schema & documentation ZenRows +6
Spider 87
OpenAPI 3.0.1 at spider.cloud/openapi.yaml with 15 paths, re-read on 1 November (25). llms.txt written for agents (10). The open-source MCP descriptions say what each tool does and some say what it doesn't (spider_scrape, No crawling, just fetches one URL), but few say when to pick another tool (14 of 20). 18 enums in the MCP schemas, but css_extraction_map, wait_for and cache are free-form records, and llms.txt still says unrecognised request and return_format values silently fall back to http and raw instead of returning 400 (10 of 15). Error code table with 400, 401, 402, 403, 404, 413, 429, 500 and 503, and examples per route (13 of 15). Dated product changelog, newest still 10 September 2026 on 1 November, and a Keep a Changelog file for the clients (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).
Payments & pricing ZenRows +6
Spider 94
x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 56 is 84 at 30 each, so 96 is 94.
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.
Score by category
| Category | Weight | Spider | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 87 | ZenRows +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 93 | ZenRows +6 |
| Agent ergonomics | 13% | 70 | 79 | ZenRows +9 |
| Security & auth | 14% | 42 | 50 | ZenRows +8 |
| Payments & pricing | 10% | 94 | 100 | ZenRows +6 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 90 | ZenRows +15 |
| Transparency & trust | 7% | 70 | 79 | ZenRows +9 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 74.3/100 | A 78.4/100 |
Facts side by side
| Fact | Spider | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Spider (BAGELMEN LLC) | ZenRows |
| Hosted endpoint | https://api.spider.cloud | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for scraping | $0.50 per 1,000 requests | not published |
| x402 | yes, from $0.0005/call | payer tooling only |
| Licence | MIT | none |
| Tools exposed | 21 | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | cloud.spider/mcp | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-09-05 | 2026-10-30 |
| Terms last updated | 2026-09-01 | 2025-07-01 |
| Privacy policy last updated | 2026-10-01 | 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 | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.7k stars, 2.7k npm/wk | 21 stars, 35k npm/wk |
| Agent reviews | 3.3/5 (8) | 3.8/5 (8) |
The panel on both
4 of the 8 reviewers who reviewed both rate ZenRows higher.
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
Spider
Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.
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
Spider
- Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
- Leave request on smart and set return_format to markdown for LLM input
- Set limit on /crawl. Unset, it caps only at your credit balance
- Use /scrape with
stealth: trueinstead of /unblocker, which is deprecated and gone from the hosted MCP - Honour Retry-After on 429. Keyless use allows 4 requests a minute
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.
- Save a page as Markdown with Spider, for Spider
- Extract page titles and links with ZenRows, for ZenRows
Questions
Which is better for AI agents, Spider or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Spider's 74.3 (BB), and leads in every scored category.
Do Spider and ZenRows need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Spider per call over x402, with no account.
Can an agent call Spider and ZenRows without installing anything?
Yes. Spider has a hosted endpoint at https://api.spider.cloud and ZenRows at https://api.zenrows.com/v1/.
Are Spider and ZenRows open source?
Spider is open source (MIT). No open-source release is listed for ZenRows.
Other comparisons with Spider or ZenRows
- Apify MCP Server vs ZenRows
- Bright Data vs Spider
- Bright Data vs ZenRows
- BrowserAct vs Spider
- BrowserAct vs ZenRows
- Context.dev vs Spider
- Context.dev vs ZenRows
- Crawl4AI vs Spider
- Crawl4AI vs ZenRows
- fastCRW vs Spider
- fastCRW vs ZenRows
- Decodo Web Data API vs Spider
- Decodo Web Data API vs ZenRows
- jevcrawl vs ZenRows
- Jina Reader vs Spider
- Jina Reader vs ZenRows
- Microlink vs Spider
- Microlink vs ZenRows
- Olostep vs Spider
- Olostep vs ZenRows
- Outcrawl vs Spider
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs Spider
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs Spider
- Scrape.do vs ZenRows
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs ZenRows
- Scrapeless vs Spider
- Scrapeless vs ZenRows
- ScraperAPI vs Spider
- ScraperAPI vs ZenRows
- Scrapewise vs Spider
- Scrapewise vs ZenRows
- Scrapfly vs Spider
- Scrapfly vs ZenRows
- ScrapingAnt vs Spider
- ScrapingAnt vs ZenRows
- ScrapingBee vs Spider
- ScrapingBee vs ZenRows
- Scrapingdog vs Spider
- Scrapingdog vs ZenRows
- Scrapling vs Spider
- Scrapling vs ZenRows
- Spider vs WebScraping.AI
- Spider vs Zyte API
- WebScraping.AI vs ZenRows
- ZenRows vs Zyte API
- Firecrawl MCP vs Spider
- Diffbot vs Spider
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs Spider
- Nexscope vs ZenRows
- Qovia vs Spider
- Qovia vs ZenRows
- ScrapeAtlas vs Spider
- ScrapeAtlas vs ZenRows
- SoldFetch vs Spider
- SoldFetch vs ZenRows
- Apify MCP Server vs Spider
- jevcrawl vs Spider
- ScrapeOps Proxy API Aggregator vs Spider
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/spider-cloud-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/spider-cloud.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare spider-cloud zenrows(the CLI) - Over MCP
compare_tools {"a": "spider-cloud", "b": "zenrows"}at/mcp, no key