# Scrape.do vs XCrawl (slim)

> Scrape.do scores 44.5 (E) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

Scrape.do scores 44.5 (E) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- Scrape.do: E 44.5, rank #1305 of 1563 · https://www.anchorterminal.com/tools/scrape-do.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- Scrape.do, good for Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side. Ahead on Reliability, 40 against 15; Schema & documentation, 57 against 35; Security & auth, 23 against 18; Payments & pricing, 53 against 30; Maintenance & community, 25 against 17; Transparency & trust, 49 against 43.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints. Also Runs on your own machine.

| Category | Scrape.do | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 40 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 35 |
| Agent ergonomics (13%) | 62 | 59 |
| Security & auth (14%) | 23 | 18 |
| Payments & pricing (10%) | 53 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 25 | 17 |
| Transparency & trust (7%) | 49 | 43 |

| Fact (where they differ) | Scrape.do | XCrawl |
| --- | --- | --- |
| Vendor | Scrape.do | XCrawl |
| Hosted endpoint | `https://api.scrape.do/` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | HTTP | Streamable HTTP, stdio |
| Tools exposed | none | 7 |
| llms.txt | yes | no |
| Last release | 2026-07-31 | 2026-04-13 |
| Terms restrict automated access | yes | not found in the text |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Reliability, Scrape.do +25: Scrape.do 40 (No public status page.); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Payments & pricing, Scrape.do +23: Scrape.do 53 (No x402, MPP or L402. The pricing page lists card, crypto and bank wire (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Schema & documentation, Scrape.do +22: Scrape.do 57 (No OpenAPI file found (0 of 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).)
- Maintenance & community, Scrape.do +8: Scrape.do 25 (The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10).); 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).)
- Transparency & trust, Scrape.do +6: Scrape.do 49 (Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15).); XCrawl 43 (A closed service.)
- Security & auth, Scrape.do +5: Scrape.do 23 (One account token, documented as the `token` query parameter on the main API, in the proxy username on proxy mode and in an `X-Token` header only on the async A…); 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).)
