# Scrape.do vs XCrawl

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

- Canonical: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl
- Markdown: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl.md (~5,100 tokens)
- Slim: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl.min.md (~880 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-20

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: grade E, 44.5/100, rank #1305 of 1563. Markdown https://www.anchorterminal.com/tools/scrape-do.md · JSON https://www.anchorterminal.com/api/v1/tools/scrape-do.json
- XCrawl: grade F, 30.4/100, rank #1463 of 1563. Markdown https://www.anchorterminal.com/tools/xcrawl.md · JSON https://www.anchorterminal.com/api/v1/tools/xcrawl.json
- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md
- All 601 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md

## Which one, for what

### Scrape.do (E)

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

Watch for: Token travels in the query string on the main API

### XCrawl (F)

Good for: A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

Also in its favour:
- Runs on your own machine

Watch for: Xcrawl LLC is named with no state, registration number or address, and the terms name no governing law


## Why the edge

### Reliability: Scrape.do +25

- Scrape.do (40): No public status page. status.scrape.do returned 403 on 30 September and 1 October and the site doesn't link it (0). No readable incident history, so 5 by the rubric (5). Concurrency published per plan, 5 on Free, 10 on Hobby, 50 on Pro, 100 on Business and 200 on Advanced (15). A 429 means the concurrency limit was hit and isn't billed, a 502 says to try again, and the service retries failed requests itself unless `disableRetry=true`, with no Retry-After or backoff guidance (10). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10). All per the 1 October check, not re-read on 5 November, since Scrape.do's terms bar automated access to its website. 0+5+15+10+0+10 = 40.
- XCrawl (15): No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30). No rate limits with numbers. The pricing page says only that Scale plans get higher rate limits (0 of 15). No 429 or overload guidance in the docs. The Python SDK retries 500, 502, 503 and 504 with backoff, but not 429 (0 of 15). The terms mention a Service Level Agreement "if applicable", and none is published (0 of 10). The API is sold publicly with no beta label (10). Total 15.

### Payments & pricing: Scrape.do +23

- Scrape.do (53): No x402, MPP or L402. The pricing page lists card, crypto and bank wire (0). Credit costs per request type and per domain are public, but credits come only with monthly plans, with no pay-as-you-go (15 of 20). Free plan, 1,000 successful requests a month with every feature, no card (20). A person signs up in a browser to get a token (0). Pricing per the 1 October check, not re-read on 5 November. 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
- XCrawl (30): No x402, MPP or L402 (0). The pricing page's plan table and credit table did not appear in the served page, and the docs give credit costs only in examples (1 for a plain scrape, 2 for a search), so pricing is scored absent (0 of 30, unchecked). 1,000 free credits on signup with no card (30). A person signs up in a browser at dash.xcrawl.com to get a key (0). Total 30.

### Schema & documentation: Scrape.do +22

- Scrape.do (57): No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on `super` or `render` and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15, held as a partial). All per the 1 October check, not re-read on 5 November. 0+10+12+10+13+12 = 57.
- 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). llms.txt returns 404. The docs have "Copy page" buttons, and the xcrawl-skills repository has Markdown skill files for agents (5 of 10). Each API reference page states what the endpoint does, with no guidance on when not to use it (8 of 20). Parameter tables give types, required flags, defaults and enums for formats, device and wait_until. cookies and headers are free maps (11 of 15). Request and response examples on every reference page, but no error responses or codes documented outside the MCP troubleshooting table (6 of 15). Versioned /v1 paths and no changelog (5 of 15). Total 35.

### 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). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.
- 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). Nothing dated in the 90 days from 22 August 2026 (0 of 20). We couldn't read GitHub issues. There is no public changelog, and support is by email, Telegram, WhatsApp and Microsoft Teams, with a 24-hour reply promised in the footer (5 of 15). Official Python and Node.js SDKs, unchanged for seven months (10 of 15). The SDK repository has 3 commits, no tests and no CI. Dependencies are current (2 of 10). Total 17.

### Transparency & trust: Scrape.do +6

- Scrape.do (49): Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15). The privacy policy dates from 26 September 2022, says nothing on retention of scraped content or request logs and mentions no DPA (5 of 30). Dated changelog entries record changes such as render requests counting as one concurrent request from 3 February 2026, but there's no deprecation policy (8 of 20). Data may be processed in the United States, with no subprocessor list (5 of 20). Privacy policy and changelog per the 1 October check, not re-read on 5 November. 15+5+8+5 = 33.
- XCrawl (43): A closed service. The SDKs are MIT, and the MCP package is UNLICENSED with no repository. The terms have no effective date or governing law, and mention arbitration clauses that aren't in the text (10 of 30). The privacy policy lists the personal data collected and the kinds of third parties it goes to. It gives no retention periods and says nothing on scraped content. The terms mention a Data Protection Addendum that isn't linked (8 of 30). No deprecation policy or dated notices (0 of 20). Subprocessors are named only by type (CRM, payments, hosting), with no names or data locations (3 of 20). Total 21.

### 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 API. We found no scopes or rotation for it. Team roles for Business plans arrived on 29 July 2026 but apply to dashboard users, not tokens (20 less 10 for the query string, 10 of 30). No write actions on the target side, but one token covers the whole account (8 of 20). Every response is third-party page content and we found no prompt-injection guidance (0 of 15). Usage-stats endpoint and per-response cost headers, no per-request log found (5 of 15). No security.txt, security page or disclosure policy found. Proxy mode needs Scrape.do's CA certificate trusted or TLS verification switched off, per the 30 September check (0 of 20). Docs per the 1 October check, not re-read on 5 November. 10+8+0+5+0 = 23.
- 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). The recommended hosted MCP setup puts the key in the URL path, so less 10, read the way the checklist reads a key in a query string (10 of 30). The API only reads third-party pages and has no destructive account actions, but there is no read-only or least-privilege key (5 of 20). No prompt-injection guidance in the docs or the skills (0 of 15). Each response reports credits used, and xcrawl_key_status gives the balance, with no request log found (3 of 15). No security.txt, disclosure policy or bug bounty. The ISO 27001 badge on the home page links to no certificate or security page (0 of 20). Total 18.

## Score by category

| Category | Weight | Scrape.do | XCrawl | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 40 | 15 | Scrape.do +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 35 | Scrape.do +22 |
| Agent ergonomics | 13% | 62 | 59 | Scrape.do +3 |
| Security & auth | 14% | 23 | 18 | Scrape.do +5 |
| Payments & pricing | 10% | 53 | 30 | Scrape.do +23 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 17 | Scrape.do +8 |
| Transparency & trust | 7% | 49 | 43 | Scrape.do +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **44.5 · E** | **30.4 · F** | |

## Facts side by side

| Fact | Scrape.do | XCrawl |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | XCrawl |
| Hosted endpoint | `https://api.scrape.do/` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | HTTP | Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-07-31 | 2026-04-13 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 3.5/5 (2) | none |

## How the scores have moved

### Scrape.do

- +2.3 on 13 November 2026: checklist
- -1.8 on 5 November 2026: time
- +0.3 on 27 October 2026: checklist

### XCrawl

No score change since it was listed.

## Verdicts

**Scrape.do.** $29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. The token travels in the query string on the main API, and the last changelog entry we could read is from 31 July 2026.

**XCrawl.** A scrape, search, map and crawl API with 7 MCP tools, MIT Python and Node.js SDKs and 1,000 free credits without a card. Xcrawl LLC gives no address or registration. There is no OpenAPI spec, status page, rate limit, error reference or changelog, plan prices did not render for us, and the hosted MCP key travels in the URL.

## Before you call either

### Scrape.do

1. Start with the default data centre request (1 credit). Add `super=true` or `render=true` only after a block, since they cost 10 and 5
2. Pass `output=markdown` to get LLM-ready text instead of raw HTML
3. Read `Scrape.do-Request-Cost` from the response headers. Some domains cost 10 to 200 credits whatever you pass
4. Treat a 429 as too many concurrent requests and wait for one to finish
5. Keep URLs with `token=` out of logs and shared traces

### XCrawl

1. Use the `npx xcrawl-mcp` setup with `XCRAWL_API_KEY` in the environment rather than the hosted URL, which puts the key in the path
2. Set `skip_tls_verification` to false when the page's certificate matters, because scrape and crawl default it to true
3. Set `crawler.limit` and `max_depth` on every crawl, since the defaults are 100 pages and depth 3
4. Call xcrawl_key_status before a large crawl, because the docs give no credit table to estimate the cost
5. Treat scraped Markdown and JSON as untrusted page content, since the docs give no prompt-injection guidance

## Questions

### Which is better for AI agents, Scrape.do or XCrawl?

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

### Do Scrape.do and XCrawl need an API key?

Both need an API key.

### Can an agent call Scrape.do and XCrawl without installing anything?

Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl.json, and with the fewest tokens: https://www.anchorterminal.com/compare/scrape-do-vs-xcrawl.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "scrape-do", "b": "xcrawl"}`. From a terminal: `anchor compare scrape-do xcrawl`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/scrape-do.json and https://www.anchorterminal.com/api/v1/tools/xcrawl.json

## Other comparisons with Scrape.do or XCrawl

- [Apify MCP Server vs Scrape.do](https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.md)
- [Bright Data vs Scrape.do](https://www.anchorterminal.com/compare/bright-data-vs-scrape-do.md)
- [Bright Data vs XCrawl](https://www.anchorterminal.com/compare/bright-data-vs-xcrawl.md)
- [BrowserAct vs Scrape.do](https://www.anchorterminal.com/compare/browseract-vs-scrape-do.md)
- [BrowserAct vs XCrawl](https://www.anchorterminal.com/compare/browseract-vs-xcrawl.md)
- [Context.dev vs Scrape.do](https://www.anchorterminal.com/compare/context-dev-vs-scrape-do.md)
- [Context.dev vs XCrawl](https://www.anchorterminal.com/compare/context-dev-vs-xcrawl.md)
- [Crawl4AI vs Scrape.do](https://www.anchorterminal.com/compare/crawl4ai-vs-scrape-do.md)
- [Crawl4AI vs XCrawl](https://www.anchorterminal.com/compare/crawl4ai-vs-xcrawl.md)
- [fastCRW vs Scrape.do](https://www.anchorterminal.com/compare/crw-vs-scrape-do.md)
- [fastCRW vs XCrawl](https://www.anchorterminal.com/compare/crw-vs-xcrawl.md)
- [Decodo Web Data API vs Scrape.do](https://www.anchorterminal.com/compare/decodo-vs-scrape-do.md)
- [Decodo Web Data API vs XCrawl](https://www.anchorterminal.com/compare/decodo-vs-xcrawl.md)
- [Diffbot vs Scrape.do](https://www.anchorterminal.com/compare/diffbot-vs-scrape-do.md)
- [jevcrawl vs Scrape.do](https://www.anchorterminal.com/compare/jevcrawl-vs-scrape-do.md)
- [Jina Reader vs Scrape.do](https://www.anchorterminal.com/compare/jina-reader-vs-scrape-do.md)
- [Jina Reader vs XCrawl](https://www.anchorterminal.com/compare/jina-reader-vs-xcrawl.md)
- [Microlink vs Scrape.do](https://www.anchorterminal.com/compare/microlink-vs-scrape-do.md)
- [Microlink vs XCrawl](https://www.anchorterminal.com/compare/microlink-vs-xcrawl.md)
- [Olostep vs Scrape.do](https://www.anchorterminal.com/compare/olostep-vs-scrape-do.md)
- [Olostep vs XCrawl](https://www.anchorterminal.com/compare/olostep-vs-xcrawl.md)
- [Outcrawl vs Scrape.do](https://www.anchorterminal.com/compare/outcrawl-vs-scrape-do.md)
- [Outcrawl vs XCrawl](https://www.anchorterminal.com/compare/outcrawl-vs-xcrawl.md)
- [Oxylabs Web Scraper API vs Scrape.do](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrape-do.md)
- [Oxylabs Web Scraper API vs XCrawl](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-xcrawl.md)
- [Scrape.do vs ScrapeGraphAI](https://www.anchorterminal.com/compare/scrape-do-vs-scrapegraphai.md)
- [Scrape.do vs Scrapeless](https://www.anchorterminal.com/compare/scrape-do-vs-scrapeless.md)
- [Scrape.do vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/scrape-do-vs-scrapeops.md)
- [Scrape.do vs ScraperAPI](https://www.anchorterminal.com/compare/scrape-do-vs-scraperapi.md)
- [Scrape.do vs Scrapewise](https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.md)
- [Scrape.do vs Scrapfly](https://www.anchorterminal.com/compare/scrape-do-vs-scrapfly.md)
- [Scrape.do vs ScrapingAnt](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingant.md)
- [Scrape.do vs ScrapingBee](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingbee.md)
- [Scrape.do vs Scrapingdog](https://www.anchorterminal.com/compare/scrape-do-vs-scrapingdog.md)
- [Scrape.do vs Scrapling](https://www.anchorterminal.com/compare/scrape-do-vs-scrapling.md)
- [Scrape.do vs Spider](https://www.anchorterminal.com/compare/scrape-do-vs-spider-cloud.md)
- [Scrape.do vs WebScraping.AI](https://www.anchorterminal.com/compare/scrape-do-vs-webscraping-ai.md)
- [Scrape.do vs ZenRows](https://www.anchorterminal.com/compare/scrape-do-vs-zenrows.md)
- [Scrape.do vs Zyte API](https://www.anchorterminal.com/compare/scrape-do-vs-zyte.md)
- [ScrapeGraphAI vs XCrawl](https://www.anchorterminal.com/compare/scrapegraphai-vs-xcrawl.md)
- [Scrapeless vs XCrawl](https://www.anchorterminal.com/compare/scrapeless-vs-xcrawl.md)
- [ScraperAPI vs XCrawl](https://www.anchorterminal.com/compare/scraperapi-vs-xcrawl.md)
- [Scrapewise vs XCrawl](https://www.anchorterminal.com/compare/scrapewise-vs-xcrawl.md)
- [Scrapfly vs XCrawl](https://www.anchorterminal.com/compare/scrapfly-vs-xcrawl.md)
- [ScrapingAnt vs XCrawl](https://www.anchorterminal.com/compare/scrapingant-vs-xcrawl.md)
- [ScrapingBee vs XCrawl](https://www.anchorterminal.com/compare/scrapingbee-vs-xcrawl.md)
- [Scrapingdog vs XCrawl](https://www.anchorterminal.com/compare/scrapingdog-vs-xcrawl.md)
- [Scrapling vs XCrawl](https://www.anchorterminal.com/compare/scrapling-vs-xcrawl.md)
- [Spider vs XCrawl](https://www.anchorterminal.com/compare/spider-cloud-vs-xcrawl.md)
- [WebScraping.AI vs XCrawl](https://www.anchorterminal.com/compare/webscraping-ai-vs-xcrawl.md)
- [XCrawl vs ZenRows](https://www.anchorterminal.com/compare/xcrawl-vs-zenrows.md)
- [XCrawl vs Zyte API](https://www.anchorterminal.com/compare/xcrawl-vs-zyte.md)
- [Firecrawl MCP vs XCrawl](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-xcrawl.md)
- [Diffbot vs XCrawl](https://www.anchorterminal.com/compare/diffbot-vs-xcrawl.md)
- [Nexscope vs XCrawl](https://www.anchorterminal.com/compare/nexscope-vs-xcrawl.md)
- [Qovia vs XCrawl](https://www.anchorterminal.com/compare/qovia-vs-xcrawl.md)
- [ScrapeAtlas vs XCrawl](https://www.anchorterminal.com/compare/scrapeatlas-vs-xcrawl.md)
- [SoldFetch vs XCrawl](https://www.anchorterminal.com/compare/soldfetch-vs-xcrawl.md)
- [Apify MCP Server vs XCrawl](https://www.anchorterminal.com/compare/apify-mcp-vs-xcrawl.md)
- [jevcrawl vs XCrawl](https://www.anchorterminal.com/compare/jevcrawl-vs-xcrawl.md)
- [Firecrawl MCP vs Scrape.do](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrape-do.md)
- [ScrapeOps Proxy API Aggregator vs XCrawl](https://www.anchorterminal.com/compare/scrapeops-vs-xcrawl.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
