# Context.dev vs XCrawl (slim)

> Context.dev scores 78.8 (A) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

Context.dev scores 78.8 (A) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- Context.dev: A 78.8, rank #44 of 1563 · https://www.anchorterminal.com/tools/context-dev.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- Context.dev, good for Agents that need one call for Markdown, screenshots and schema-shaped JSON from a page, plus batches, monitors and search on the same balance, and teams that also want brand data. Ahead on Reliability, 67 against 15; Schema & documentation, 96 against 35; Agent ergonomics, 90 against 59; Security & auth, 83 against 18; Payments & pricing, 75 against 30; Maintenance & community, 85 against 17; Transparency & trust, 78 against 43. Also Agent-ready, a grade of BB or better.
- 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; No incidents deducted, where Context.dev loses 3 points for them.

| Category | Context.dev | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 67 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 96 | 35 |
| Agent ergonomics (13%) | 90 | 59 |
| Security & auth (14%) | 83 | 18 |
| Payments & pricing (10%) | 75 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 17 |
| Transparency & trust (7%) | 78 | 43 |

| Fact (where they differ) | Context.dev | XCrawl |
| --- | --- | --- |
| Vendor | Context Dev Inc. | XCrawl |
| Hosted endpoint | `https://api.context.dev/v1` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Price for scraping | $0.79 per 1,000 pages | not published |
| Tools exposed | 42 | 7 |
| llms.txt | yes | no |
| Last release | 2026-10-31 | 2026-04-13 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 5 stars, 62k npm/wk, 10k PyPI/wk | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Maintenance & community, Context.dev +68: Context.dev 85 (TypeScript SDK 3.21.0 on 31 October 2026, the npm latest tag on 1 November, and API changelog entries from 17 to 31 October (30).); 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).)
- Security & auth, Context.dev +65: Context.dev 83 (Restricted keys scoped to data calls, logs, monitors, batches and, since 28 October, access policies on every plan, revocable, with a documented rotation proces…); 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).)
- Schema & documentation, Context.dev +61: Context.dev 96 (Public OpenAPI 3.1 at www.context.dev/openapi.json, 38 paths and 42 operations with operation IDs and typed request and response schemas on 1 November, now with…); 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).)
- Reliability, Context.dev +52: Context.dev 67 (Better Stack status page at status.context.dev with 90 days of per-endpoint history, but its monitors, re-read on 1 November, cover the older per-format routes…); 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, Context.dev +45: Context.dev 75 (No x402, MPP or L402 in llms.txt, the pricing page or the OpenAPI file on 1 November (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Transparency & trust, Context.dev +35: Context.dev 78 (Closed service.); XCrawl 43 (A closed service.)
