# WebScraping.AI vs XCrawl (slim)

> WebScraping.AI scores 63.9 (B) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/webscraping-ai-vs-xcrawl.md (~5,350 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/compare/webscraping-ai-vs-xcrawl.json · canonical https://www.anchorterminal.com/compare/webscraping-ai-vs-xcrawl
- 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)

WebScraping.AI scores 63.9 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- WebScraping.AI: B 63.9, rank #618 of 1563 · https://www.anchorterminal.com/tools/webscraping-ai.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- WebScraping.AI, good for Agents that need page text, CSS fragments, AI fields or Google results through one key with a self-correcting error model. Ahead on Reliability, 43 against 15; Schema & documentation, 89 against 35; Agent ergonomics, 95 against 59; Security & auth, 36 against 18; Payments & pricing, 60 against 30; Maintenance & community, 82 against 17; Transparency & trust, 51 against 43.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

| Category | WebScraping.AI | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 43 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 35 |
| Agent ergonomics (13%) | 95 | 59 |
| Security & auth (14%) | 36 | 18 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 17 |
| Transparency & trust (7%) | 51 | 43 |

| Fact (where they differ) | WebScraping.AI | XCrawl |
| --- | --- | --- |
| Vendor | Urlooker LLC | XCrawl |
| Hosted endpoint | `https://mcp.webscraping.ai/mcp` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Auth | OAuth or key | API key |
| Tools exposed | 10 | 7 |
| llms.txt | yes | no |
| MCP registry | `io.github.webscraping-ai/webscraping-ai` | not listed |
| Last release | 2026-10-26 | 2026-04-13 |
| Terms restrict automated access | yes | not found in the text |

Why the edge:
- Maintenance & community, WebScraping.AI +65: WebScraping.AI 82 (Read for a closed service with open clients.); 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).)
- Schema & documentation, WebScraping.AI +54: WebScraping.AI 89 (OpenAPI file (version 3.2.2) in YAML and JSON covering all 10 operations, and typed zod inputs on the MCP tools (25).); 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).)
- Agent ergonomics, WebScraping.AI +36: WebScraping.AI 95 (Ten MCP tools (25).); XCrawl 59 (7 MCP tools per the Claude Code guide, compact by name and description, though the definitions themselves couldn't be read (22 of 25).)
- Payments & pricing, WebScraping.AI +30: WebScraping.AI 60 (No x402, MPP or L402 (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Reliability, WebScraping.AI +28: WebScraping.AI 43 (Graded on the hosted lines.); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Security & auth, WebScraping.AI +18: WebScraping.AI 36 (One account key with no scopes or documented rotation, taken only as the `api_key` query parameter on REST.); 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).)
