# ScrapeOps Proxy API Aggregator vs XCrawl (slim)

> ScrapeOps Proxy API Aggregator scores 52.9 (D) to XCrawl's 30.4 (F) for scraping proxies. Prices, MCP, x402, uptime and agent notes side by side.

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

ScrapeOps Proxy API Aggregator scores 52.9 (D) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping proxies.

- ScrapeOps Proxy API Aggregator: D 52.9, rank #1068 of 1563 · https://www.anchorterminal.com/tools/scrapeops.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- ScrapeOps Proxy API Aggregator, good for Teams that want one key across many proxy APIs, paid only on success, with cost caps per request. Ahead on Reliability, 37 against 15; Schema & documentation, 67 against 35; Agent ergonomics, 79 against 59; Security & auth, 28 against 18; Payments & pricing, 60 against 30; Maintenance & community, 46 against 17; Transparency & trust, 61 against 43.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

| Category | ScrapeOps Proxy API Aggregator | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 37 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 35 |
| Agent ergonomics (13%) | 79 | 59 |
| Security & auth (14%) | 28 | 18 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 46 | 17 |
| Transparency & trust (7%) | 61 | 43 |

| Fact (where they differ) | ScrapeOps Proxy API Aggregator | XCrawl |
| --- | --- | --- |
| Vendor | ScrapeOps Limited | XCrawl |
| Hosted endpoint | `https://mcp.scrapeops.io/mcp` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Tools exposed | 3 | 7 |
| llms.txt | yes | no |
| Last release | 2026-10 | 2026-04-13 |
| Terms restrict automated access | yes | not found in the text |

Why the edge:
- Schema & documentation, ScrapeOps Proxy API Aggregator +32: ScrapeOps Proxy API Aggregator 67 (No OpenAPI or similar spec.); 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).)
- Payments & pricing, ScrapeOps Proxy API Aggregator +30: ScrapeOps Proxy API Aggregator 60 (No x402, MPP or L402 (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Maintenance & community, ScrapeOps Proxy API Aggregator +29: ScrapeOps Proxy API Aggregator 46 (Read for a closed service.); 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).)
- Reliability, ScrapeOps Proxy API Aggregator +22: ScrapeOps Proxy API Aggregator 37 (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).)
- Agent ergonomics, ScrapeOps Proxy API Aggregator +20: ScrapeOps Proxy API Aggregator 79 (Three 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).)
- Transparency & trust, ScrapeOps Proxy API Aggregator +18: ScrapeOps Proxy API Aggregator 61 (Closed service under terms naming ScrapeOps Limited of Ireland, with an MIT MCP server (15 of 30).); XCrawl 43 (A closed service.)
