# Crawl4AI vs Scrape.do

> Scrape.do and Crawl4AI score within a point of each other for scraping, 44 and 43.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/crawl4ai-vs-scrape-do
- Markdown: https://www.anchorterminal.com/compare/crawl4ai-vs-scrape-do.md (~5,150 tokens)
- 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-07

Scrape.do and Crawl4AI score within a point of each other on agent readiness, 44 (E) and 43.9 (E). Crawl4AI leads on agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust. Both do scraping.

- Crawl4AI: grade E, 43.9/100, rank #1224 of 1486. Markdown https://www.anchorterminal.com/tools/crawl4ai.md · JSON https://www.anchorterminal.com/api/v1/tools/crawl4ai.json
- Scrape.do: grade E, 44/100, rank #1219 of 1486. Markdown https://www.anchorterminal.com/tools/scrape-do.md · JSON https://www.anchorterminal.com/api/v1/tools/scrape-do.json
- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md
- All 501 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md

## Which one, for what

### Crawl4AI (E)

Good for: Agents that need cheap page-to-Markdown at volume, Google results and search in one key, or a free self-hosted Python crawler.

Ahead on:
- Agent ergonomics, 67 against 62
- Security & auth, 46 against 23
- Payments & pricing, 45 against 35
- Maintenance & community, 83 against 45
- Transparency & trust, 70 against 49

Also in its favour:
- Open source

Watch for: No status page, SLA or OpenAPI spec for the cloud API found

### 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 35

Also in its favour:
- No incidents deducted, where Crawl4AI loses 10 points for them

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


## Why the edge

### Maintenance & community: Crawl4AI +38

- Crawl4AI (83): Library v0.9.5 on 14 October 2026, 23 days before 6 November, and the cloud added /serp on 8 October (30). v0.9.3 (31 August), v0.9.4 (23 September) and v0.9.5 (14 October) in the 90 days from 8 August (20). 56 open issues on 6 November, the newest triaged with Bug, Needs Triage, In-progress, Root caused or Done labels within days, plus a Discord. Reply authors weren't read (20 of 25). Not in the official MCP registry, and the cloud has no official SDK; the Python library is current on PyPI (8 of 15). The security workflow runs a test suite and a default-posture gate, and releases are built and checked with twine. No general test workflow on push found (5 of 10). 30 + 20 + 20 + 8 + 5 = 83.
- Scrape.do (45): Last changelog entry on 31 July 2026, a Gemini scraper API (20). Two dated entries since 3 July, 29 and 31 July, against the three the rubric asks for (10 of 20). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, hasn't shipped since 13 November 2024 (5 of 15). No public repository or CI to check (2 of 10).

### Security & auth: Crawl4AI +23

- Crawl4AI (46): Bearer keys, shown once and regenerable, with 3 to 30 keys per plan. claude.ai and ChatGPT sign in through a flow that advertises one scope, `mcp`, and each app shows as a revocable key. No per-key scopes, and the docs don't offer the key in a URL (22 of 30). A key can call billing routes, and the MCP `topup` and `recharge` tools charge the saved card, though llms.txt tells agents to ask first and accounts can set a spend cap. No read-only key (6 of 20). Scraped pages are untrusted text and no prompt-injection guidance was found in llms.txt or the API docs (0). Per-call cost, balance and fetch path in response headers and fields, no access log documented (6 of 15). The security page (4 October 2026) gives a disclosure process with fix targets and says SOC 2 is in progress, and the library publishes GitHub advisories with reporter credits. security.txt redirects to a 404, and no bounty found (12 of 20). 22 + 6 + 0 + 6 + 12 = 46.
- 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).

### Transparency & trust: Crawl4AI +21

- Crawl4AI (70): The library is Apache-2.0 and the cloud is closed under terms that name CONTEXT4AI PTE LTD (22 of 30). The privacy policy gives retention periods (account plus 90 days, usage records 13 months, logs 90 days), but none for crawled content, and llms.txt says repeated URLs are served from a shared archive while the security page says fetched pages are used only to answer the request (18 of 30). The legacy cloud API closed on 6 November 2026 with a migration guide but no dated notice found, and the terms promise notice of material changes only 'where reasonable' (8 of 20). Subprocessors named with their locations on the security page, with EU storage of account records (18 of 20). 22 + 18 + 8 + 18 = 66.
- Scrape.do (49): Closed service with published terms of use under PACKEND, LLC (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).

### Payments & pricing: Crawl4AI +10

- Crawl4AI (45): No x402, MPP or L402 (0). Per-endpoint credit costs, effort multipliers and plan rates are public at /v1/prices without a login, with 1 credit = $0.001 (20). 1,000 free credits a month, no card (20). A 7-day pass key comes from a click on api.crawl4ai.com without an account, which is still a person in a browser, and a permanent key needs email verification (5 of 20). 0 + 20 + 20 + 5 = 45.
- Scrape.do (35): 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).

### Reliability: Scrape.do +5

- Crawl4AI (35): Graded on the hosted lines, for Crawl4AI Cloud, which the README and llms.txt now lead with and which an agent calls through its MCP server; the library would read on the local lines. No status page is linked, and status.crawl4ai.com fails TLS (0). No incident history readable (5). Per-plan limits are published with numbers in /v1/prices, from 10 requests a minute and 2 at a time on Free to 1,500 and 50 on Scale (15). 429 carries X-RateLimit headers and a message, 503 busy says to resend after a few seconds, and MCP job submissions take an idempotency key, but no Retry-After or backoff guidance (10 of 15). No SLA found in the terms or pricing (0). Prices and the free credit are a soft launch, /serp is beta and /answer experimental, while scrape, extract and search carry no beta label (5 of 10). 0 + 5 + 15 + 10 + 0 + 5 = 35.
- Scrape.do (40): No public status page. status.scrape.do returned 403 to our fetch again today, as it did on 30 September, 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`, but there's no Retry-After or backoff guidance (10 of 15). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10).

### Agent ergonomics: Crawl4AI +5

- Crawl4AI (67): 16 MCP tools, six of them for billing and support (15 of 25). `format` md or html, `parse` opt-in blocks, batch limits and job results paged 500 at a time over HTTP and 50 over MCP (16 of 20). String error codes an agent can branch on (blocked, login-wall, no-answer, busy, no_credit, plan_cap, spend_cap), each with whether it is charged (18 of 20). Failed and cancelled calls aren't charged and `jobs_submit` takes an idempotency key, but no tool annotations are documented and two tools can charge the saved card (10 of 20). Only `url` or `q` is required. There is no official SDK for the cloud API; the docs give curl and standard-library Python and Node examples (8 of 15). 15 + 16 + 18 + 10 + 8 = 67.
- Scrape.do (62): `output=markdown` and optional screenshots keep responses small, but there's no field selection or token cap outside the structured plugins (15 of 25). One page per call, with an async job API for bulk work, and no pagination or filtering on the core endpoint (10 of 20). Status codes documented with billing behaviour (15 of 20). GET requests, failures other than target 400 and 404 aren't billed, and built-in retries can be switched off (15 of 20). Two required parameters, but the only official SDK is the Node client last released on 13 November 2024 (7 of 15).

## Score by category

| Category | Weight | Crawl4AI | Scrape.do | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 40 | Scrape.do +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 55 | 57 | Scrape.do +2 |
| Agent ergonomics | 13% (16.2 this run) | 67 | 62 | Crawl4AI +5 |
| Security & auth | 14% (17.5 this run) | 46 | 23 | Crawl4AI +23 |
| Payments & pricing | 10% (12.5 this run) | 45 | 35 | Crawl4AI +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 45 | Crawl4AI +38 |
| Transparency & trust | 7% (8.8 this run) | 70 | 49 | Crawl4AI +21 |
| Negative events | ≤15 | -10 | 0 | |
| **Total** | | **43.9 · E** | **44 · E** | |

## Facts side by side

| Fact | Crawl4AI | Scrape.do |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | CONTEXT4AI PTE LTD | Scrape.do |
| Hosted endpoint | `https://api.crawl4ai.com/mcp` | `https://api.scrape.do/` |
| Transports | Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| Price for scraping | $0.50 per 1,000 pages | not published |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Tools exposed | 16 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-14 | 2026-07-31 |
| Terms last updated | 2026-10-15 | no date given |
| Privacy policy last updated | 2026-10-15 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 87k stars, 368k PyPI/wk | 2 npm/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Crawl4AI

No score change since it was listed.

### Scrape.do

- +0.3 on 27 October 2026: checklist
- -0.3 on 8 October 2026: checklist

## Verdicts

**Crawl4AI.** Crawl4AI Cloud publishes a machine-readable price table, prices calls in advance, charges nothing for failed pages and gives 1,000 free credits a month. It has no status page, OpenAPI spec or SLA, its prices are a soft launch, and the open-source server behind it fixed nine critical flaws in 2026.

**Scrape.do.** $29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

## Before you call either

### Crawl4AI

1. Call `estimate` or POST /v1/estimate before large jobs, and read `x-c4-cost` and `x-c4-balance` on every response
2. Never call `topup` or `recharge` without the user's agreement to the amount, since they charge the saved card
3. Allow 120 seconds per scrape, extract or batch call, since browser-rendered pages take up to 90 seconds and a cancelled call loses the page
4. Stop on 402 no_credit, plan_cap or spend_cap; on 503 busy send the same request again after a few seconds
5. Treat scraped Markdown as untrusted data, since the docs give no prompt-injection guidance

### 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

## Questions

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

Scrape.do and Crawl4AI score within a point of each other on agent readiness, 44 (E) and 43.9 (E). Crawl4AI leads on agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust.

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

Both need an API key.

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

Yes. Crawl4AI has a hosted endpoint at https://api.crawl4ai.com/mcp and Scrape.do at https://api.scrape.do/.

### Are Crawl4AI and Scrape.do open source?

Crawl4AI is open source (Apache-2.0). No open-source release is listed for Scrape.do.


## For agents

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

## Other comparisons with Crawl4AI or Scrape.do

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

---

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