# ScrapingBee vs XCrawl (slim)

> ScrapingBee scores 62 (B) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

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

ScrapingBee scores 62 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- ScrapingBee: B 62, rank #708 of 1563 · https://www.anchorterminal.com/tools/scrapingbee.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- ScrapingBee, good for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call. Ahead on Reliability, 75 against 15; Schema & documentation, 60 against 35; Agent ergonomics, 68 against 59; Security & auth, 37 against 18; Payments & pricing, 60 against 30; Maintenance & community, 75 against 17; Transparency & trust, 65 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 | ScrapingBee | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 75 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 60 | 35 |
| Agent ergonomics (13%) | 68 | 59 |
| Security & auth (14%) | 37 | 18 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 17 |
| Transparency & trust (7%) | 65 | 43 |

| Fact (where they differ) | ScrapingBee | XCrawl |
| --- | --- | --- |
| Vendor | ScrapingBee (Oxylabs group) | XCrawl |
| Hosted endpoint | `https://app.scrapingbee.com/api/v1/` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Pricing | Paid | Freemium |
| Tools exposed | 18 | 7 |
| llms.txt | yes | no |
| Last release | 2026-09-11 | 2026-04-13 |
| Terms last updated | 2024-07-15 | no date given |
| Privacy policy last updated | 2024-07-15 | no date given |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 132 stars, 49k npm/wk, 72k PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Reliability, ScrapingBee +60: ScrapingBee 75 (status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20).); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Maintenance & community, ScrapingBee +58: ScrapingBee 75 (CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time).); 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).)
- Payments & pricing, ScrapingBee +30: ScrapingBee 60 (No x402, MPP or L402 (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Schema & documentation, ScrapingBee +25: ScrapingBee 60 (No OpenAPI spec found.); 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).)
- Transparency & trust, ScrapingBee +22: ScrapingBee 65 (Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30).); XCrawl 43 (A closed service.)
- Security & auth, ScrapingBee +19: ScrapingBee 37 (One API key per account, which the MCP notes say can be revoked (401 on revoked keys).); 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).)
