# fastCRW vs ScrapeGraphAI (slim)

> fastCRW and ScrapeGraphAI score within a point of each other for scraping, 64.3 and 63.6 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.md (~4,350 tokens) · this version ~1,680 tokens · JSON https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.json · canonical https://www.anchorterminal.com/compare/crw-vs-scrapegraphai
- 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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

fastCRW and ScrapeGraphAI score within a point of each other on agent readiness, 64.3 (B) and 63.6 (B). ScrapeGraphAI leads on payments & pricing. Both do scraping.

- fastCRW: B 64.3, rank #478 of 1486 · https://www.anchorterminal.com/tools/crw.min.md
- ScrapeGraphAI: B 63.6, rank #507 of 1486 · https://www.anchorterminal.com/tools/scrapegraphai.min.md
- fastCRW, good for Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine. Ahead on Agent ergonomics, 91 against 72; Maintenance & community, 93 against 40. Also Runs on your own machine; Free to start without a card; Open source.
- ScrapeGraphAI, good for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet. Ahead on Payments & pricing, 90 against 35.

| Category | fastCRW | ScrapeGraphAI |
| --- | --- | --- |
| Reliability (16%) | 50 | 49 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 91 | 88 |
| Agent ergonomics (13%) | 91 | 72 |
| Security & auth (14%) | 40 | 44 |
| Payments & pricing (10%) | 35 | 90 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 93 | 40 |
| Transparency & trust (7%) | 60 | 61 |

| Fact (where they differ) | fastCRW | ScrapeGraphAI |
| --- | --- | --- |
| Vendor | Nanofy OÜ | ScrapeGraphAI |
| Hosted endpoint | `https://fastcrw.com/mcp` | `https://v2-api.scrapegraphai.com` |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Price for scraping | not published | $2 per 1,000 requests |
| x402 | no | payer tooling only |
| Licence | AGPL-3.0 | none |
| Tools exposed | 11 | 20 |
| MCP registry | `io.github.fastcrw/crw` | `io.github.ScrapeGraphAI/scrapegraph-mcp` |
| Last release | 2026-11-04 | 2026-07-31 |
| Terms last updated | 2026-04-04 | 2026-06-04 |
| Privacy policy last updated | no date given | 2024-03-15 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Popularity | 1.2k stars, 881 npm/wk | 2.4k npm/wk, 46k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, ScrapeGraphAI +55: fastCRW 35 (No x402, MPP or L402 (0). Plans are public with credit costs per operation and top-up prices per block of credits, $9 per 1,000 on Hobby down to $299 per 500,000 on Scale, but top-ups need a plan, so between plan-only and per-unit (15 of 20). 500 one-off credits with no card, plus up to 500 from onboarding tasks (20). Hosted keys need a person to sign up in a browser; the free self-hosted engine runs with no account but isn't the graded surface (0). 0 + 15 + 20 + 0 = 35.); ScrapeGraphAI 90 (x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90.)
- Maintenance & community, fastCRW +53: fastCRW 93 (v0.41.0 on 4 November 2026, matching the registry and npm (30). 16 dated releases in the 90 days from 8 August, from 0.37.0 to 0.41.0 (20). Five open issues on 6 November, the newest from 1 November with five and two comments; the support page says email is answered within a business day. Reply authors weren't read (18 of 25). In the official MCP registry as io.github.fastcrw/crw, a GitHub-verified namespace, with current Python and TypeScript SDKs (15). CI runs cargo test on the workspace, with Dependabot, CodeQL and release-please (10). 30 + 20 + 18 + 15 + 10 = 93.); ScrapeGraphAI 40 (The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.)
- Agent ergonomics, fastCRW +19: fastCRW 91 (11 compact MCP tools, two of them the data-source tools added in 0.41.0. Content is capped near 15,000 characters with `truncated: true` and a resume offset, and map returns at most 100 URLs by default (20 of 25). Formats, main-content filtering, include and exclude selectors, maxLength, startIndex, limit and crawl depth and page caps (20). Errors carry `errorCode` values such as anti_bot, insufficient_credits and llm_not_available with a retry table, though an anti-bot wall answers HTTP 200 with `success: false` (19 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, cancel is idempotent and failed pages are refunded, but job starts take no idempotency key (17 of 20). Only `url` is required, with official Python and TypeScript SDKs (15). 20 + 20 + 19 + 17 + 15 = 91.); ScrapeGraphAI 72 (20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72.)