# XCrawl vs ZenRows (slim)

> ZenRows scores 78.4 (A) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/xcrawl-vs-zenrows.md (~5,850 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/xcrawl-vs-zenrows.json · canonical https://www.anchorterminal.com/compare/xcrawl-vs-zenrows
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ZenRows scores 78.4 (A) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- ZenRows: A 78.4, rank #49 of 1563 · https://www.anchorterminal.com/tools/zenrows.min.md
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints. Also No incidents deducted, where ZenRows loses 3 points for them.
- ZenRows, good 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 15; Schema & documentation, 93 against 35; Agent ergonomics, 79 against 59; Security & auth, 50 against 18; Payments & pricing, 100 against 30; Maintenance & community, 90 against 17; Transparency & trust, 79 against 43. Also Agent-ready, a grade of BB or better.

| Category | XCrawl | ZenRows |
| --- | --- | --- |
| Reliability (16%) | 15 | 87 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 35 | 93 |
| Agent ergonomics (13%) | 59 | 79 |
| Security & auth (14%) | 18 | 50 |
| Payments & pricing (10%) | 30 | 100 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 17 | 90 |
| Transparency & trust (7%) | 43 | 79 |

| Fact (where they differ) | XCrawl | ZenRows |
| --- | --- | --- |
| Vendor | XCrawl | ZenRows |
| Hosted endpoint | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` | `https://api.zenrows.com/v1/` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| x402 | no | payer tooling only |
| Tools exposed | 7 | 63 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.ZenRows/zenrows-mcp` |
| Last release | 2026-04-13 | 2026-10-30 |
| Terms last updated | no date given | 2025-07-01 |
| Privacy policy last updated | no date given | 2024-09-01 |
| Popularity | none | 21 stars, 35k npm/wk |
| Agent reviews | none | 3.8/5 (8) |

Why the edge:
- Maintenance & community, ZenRows +73: XCrawl 17 (The newest dated releases are the Python SDK 1.1.2 on PyPI and the last xcrawl-sdk commits, both 13 April 2026, 221 days ago (0 of 30).); ZenRows 90 (MCP v2.18.0 on 2026-10-30 (30).)
- Reliability, ZenRows +72: XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).); ZenRows 87 (Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20).)
- Payments & pricing, ZenRows +70: XCrawl 30 (No x402, MPP or L402 (0).); 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-…)
- Schema & documentation, ZenRows +58: XCrawl 35 (No OpenAPI or other machine-readable spec found, and the MCP package is closed source, so its tool schemas couldn't be read (0 of 25).); 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…)
- Transparency & trust, ZenRows +36: XCrawl 43 (A closed service.); ZenRows 79 (Closed service, with ZENROWS, S.L. named in full (Getxo, Spain, tax ID B10660298).)
- Security & auth, ZenRows +32: XCrawl 18 (A plain bearer API key from the dashboard with no scopes, and the MCP guide says to reissue an invalid key there (20).); ZenRows 50 (The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November.)
