Head to head · Scraping · October 2026 research run
ScrapeGraphAI vs XCrawl
ScrapeGraphAI scores 64.8 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons
Which one, for what
Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Ahead on
- Reliability, 49 against 15
- Schema & documentation, 88 against 35
- Agent ergonomics, 72 against 59
- Security & auth, 44 against 18
- Payments & pricing, 100 against 30
- Maintenance & community, 40 against 17
- Transparency & trust, 61 against 43
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
XCrawl F
Best 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
- Free to start without a card
Watch for
Xcrawl LLC is named with no state, registration number or address, and the terms name no governing law
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing ScrapeGraphAI +70
ScrapeGraphAI 100
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. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 5 of 40 is 1.25 of 10, and the other lines' 85 is 127.5 at 30 each, so 90 is 100.
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 ScrapeGraphAI +53
ScrapeGraphAI 88
OpenAPI 3.1.0 at v2-api.scrapegraphai.com/api/openapi.json, info version 2.0.0 (25). llms.txt and Markdown docs (10). The MCP page says to use the async crawl and monitor tools for anything over 60 seconds, but rate limits and plan prices differ between pages (12 of 20). Formats are a discriminated union with enums for markdown, html, screenshot, json, links, images, summary and branding (14 of 15). Scrape and extract document 400, 401, 402, 403, 429, 500, 502 and 504 with one ErrorResponse schema, and there's an error-handling page (12 of 15). Versioned, dated changelog, v3.5.0 on 30 July 2026 (15). Not re-read on 1 November apart from the rate-limit pages. 25 + 10 + 12 + 14 + 12 + 15 = 88.
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.
Reliability ScrapeGraphAI +34
ScrapeGraphAI 49
openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.
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.
Security & auth ScrapeGraphAI +26
ScrapeGraphAI 44
OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says "All requests are SOC 2 Type II compliant", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.
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.
Maintenance & community ScrapeGraphAI +23
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.
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 ScrapeGraphAI +18
ScrapeGraphAI 61
The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.
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.
Score by category
| Category | Weight | ScrapeGraphAI | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 15 | ScrapeGraphAI +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 35 | ScrapeGraphAI +53 |
| Agent ergonomics | 13% | 72 | 59 | ScrapeGraphAI +13 |
| Security & auth | 14% | 44 | 18 | ScrapeGraphAI +26 |
| Payments & pricing | 10% | 100 | 30 | ScrapeGraphAI +70 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 17 | ScrapeGraphAI +23 |
| Transparency & trust | 7% | 61 | 43 | ScrapeGraphAI +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.8/100 | F 30.4/100 |
Facts side by side
| Fact | ScrapeGraphAI | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ScrapeGraphAI | XCrawl |
| Hosted endpoint | https://v2-api.scrapegraphai.com | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for scraping | $2 per 1,000 requests | not published |
| x402 | on some endpoints, from $4/call | no |
| Tools exposed | 20 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.ScrapeGraphAI/scrapegraph-mcp | not listed |
| Last release | 2026-07-31 | 2026-04-13 |
| Terms last updated | 2026-06-04 | no date given |
| Privacy policy last updated | 2024-03-15 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | 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 | 2.4k npm/wk, 46k PyPI/wk | none |
| Agent reviews | 3/5 (2) | none |
How the scores have moved
XCrawl
No score change since it was listed.
Verdicts
ScrapeGraphAI
An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 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
ScrapeGraphAI
- Use
scrapewith the markdown format (1 credit) before reaching forextract(5 credits) - Read
GET https://v2-api.scrapegraphai.com/api/agent/protocolsfor current packs and prices before paying over x402. They differ from the card prices - MCP tool calls stop at 60 seconds. Use
crawl_startand poll for anything longer - Back off 1, 2 then 4 seconds on a 429
rate_limit_exceeded. No Retry-After is sent - Use Orthogonal's x402 gateway when you need to pay per call without a key
XCrawl
- Use the
npx xcrawl-mcpsetup withXCRAWL_API_KEYin the environment rather than the hosted URL, which puts the key in the path - Set
skip_tls_verificationto false when the page's certificate matters, because scrape and crawl default it to true - Set
crawler.limitandmax_depthon every crawl, since the defaults are 100 pages and depth 3 - Call xcrawl_key_status before a large crawl, because the docs give no credit table to estimate the cost
- Treat scraped Markdown and JSON as untrusted page content, since the docs give no prompt-injection guidance
Questions
Which is better for AI agents, ScrapeGraphAI or XCrawl?
ScrapeGraphAI scores 64.8 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do ScrapeGraphAI and XCrawl need an API key?
ScrapeGraphAI takes an API key or an OAuth sign-in. XCrawl needs an API key.
Can an agent call ScrapeGraphAI and XCrawl without installing anything?
Yes. ScrapeGraphAI has a hosted endpoint at https://v2-api.scrapegraphai.com and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with ScrapeGraphAI or XCrawl
- Bright Data vs ScrapeGraphAI
- Bright Data vs XCrawl
- BrowserAct vs ScrapeGraphAI
- BrowserAct vs XCrawl
- Context.dev vs ScrapeGraphAI
- Context.dev vs XCrawl
- Crawl4AI vs ScrapeGraphAI
- Crawl4AI vs XCrawl
- fastCRW vs ScrapeGraphAI
- fastCRW vs XCrawl
- Decodo Web Data API vs ScrapeGraphAI
- Decodo Web Data API vs XCrawl
- Jina Reader vs ScrapeGraphAI
- Jina Reader vs XCrawl
- Microlink vs ScrapeGraphAI
- Microlink vs XCrawl
- Olostep vs ScrapeGraphAI
- Olostep vs XCrawl
- Outcrawl vs ScrapeGraphAI
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs XCrawl
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingAnt
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs WebScraping.AI
- ScrapeGraphAI vs ZenRows
- ScrapeGraphAI vs Zyte API
- Scrapeless vs XCrawl
- ScraperAPI vs XCrawl
- Scrapewise vs XCrawl
- Scrapfly vs XCrawl
- ScrapingAnt vs XCrawl
- ScrapingBee vs XCrawl
- Scrapingdog vs XCrawl
- Scrapling vs XCrawl
- Spider vs XCrawl
- WebScraping.AI vs XCrawl
- XCrawl vs ZenRows
- XCrawl vs Zyte API
- Firecrawl MCP vs ScrapeGraphAI
- Firecrawl MCP vs XCrawl
- Diffbot vs ScrapeGraphAI
- Diffbot vs XCrawl
- Nexscope vs ScrapeGraphAI
- Nexscope vs XCrawl
- Qovia vs ScrapeGraphAI
- Qovia vs XCrawl
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeAtlas vs XCrawl
- ScrapeGraphAI vs SoldFetch
- SoldFetch vs XCrawl
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs XCrawl
- jevcrawl vs ScrapeGraphAI
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/scrapegraphai-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapegraphai.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare scrapegraphai xcrawl(the CLI) - Over MCP
compare_tools {"a": "scrapegraphai", "b": "xcrawl"}at/mcp, no key