# ScraperAPI vs XCrawl (slim)

> ScraperAPI scores 52.2 (D) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

ScraperAPI scores 52.2 (D) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- ScraperAPI: D 52.2, rank #1096 of 1563 · https://www.anchorterminal.com/tools/scraperapi.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- ScraperAPI, good for Agents that want a single GET to fetch pages through proxies, with parsed JSON for Amazon, Google, Walmart, eBay and Redfin and a batch API of up to 50,000 URLs. Ahead on Reliability, 42 against 15; Schema & documentation, 67 against 35; Agent ergonomics, 74 against 59; Security & auth, 29 against 18; Payments & pricing, 60 against 30; Maintenance & community, 41 against 17; Transparency & trust, 54 against 43.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

| Category | ScraperAPI | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 42 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 35 |
| Agent ergonomics (13%) | 74 | 59 |
| Security & auth (14%) | 29 | 18 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 41 | 17 |
| Transparency & trust (7%) | 54 | 43 |

| Fact (where they differ) | ScraperAPI | XCrawl |
| --- | --- | --- |
| Vendor | ScraperAPI (saas.group) | XCrawl |
| Hosted endpoint | `https://api.scraperapi.com` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Tools exposed | 28 | 7 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-08-07 | 2026-04-13 |
| Terms last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 5 stars | none |

Why the edge:
- Schema & documentation, ScraperAPI +32: ScraperAPI 67 (No OpenAPI file found.); 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, ScraperAPI +30: ScraperAPI 60 (No x402, MPP or L402 found in the docs index or pricing page (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Reliability, ScraperAPI +27: ScraperAPI 42 (No status page is linked from the home, pricing, support or docs pages we read on 9 October or 4 November (0).); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Maintenance & community, ScraperAPI +24: ScraperAPI 41 (The newest dated entry is the October 2026 release note on automatic Akamai unblocking, dated by month only.); 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).)
- Agent ergonomics, ScraperAPI +15: ScraperAPI 74 (28 MCP tools with no toolsets or dynamic loading (15 of 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).)
- Security & auth, ScraperAPI +11: ScraperAPI 29 (One API key per account, regenerated from the dashboard at most once every 24 hours.); 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).)
