Head to head · Scraping · October 2026 research run
Scrapfly vs XCrawl
Scrapfly scores 77 (BB) 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
Scrapfly BB
Best for An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on.
Ahead on
- Reliability, 85 against 15
- Schema & documentation, 95 against 35
- Agent ergonomics, 80 against 59
- Security & auth, 75 against 18
- Payments & pricing, 60 against 30
- Maintenance & community, 84 against 17
- Transparency & trust, 75 against 43
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
The open-source MCP server registers 62 tools at once, a heavy tools/list
XCrawl F
Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.
Also in its favour
- No incidents deducted, where Scrapfly loses 3 points for them
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.
Reliability Scrapfly +70
Scrapfly 85
scrapfly.io/status answers with Statuspage's status JSON, which names its page as scrapfly.statuspage.io. That page has 25 components and incident history back to 2022, read through its history feed on 1 November. The 1 October check read only the overall state and found no history (20, was 10). The newest incident is a Scrapium rendering fault on 21 May 2026, so nothing is posted in the 90 days from 3 August (30, was 5). Concurrency per plan is published (5 on Discovery to 100 on Enterprise) and each project has a configurable per-minute throttle (15). The error catalogue marks every code retryable or not and has three ERR::THROTTLE codes, but we found no Retry-After header or backoff guidance on the errors or throttling pages (10 of 15). The terms disclaim uptime and no uptime SLA is published, and the pricing page's SLA mentions cover support response on Enterprise (0). The Scrape API is GA. Vault and alerting are beta, outside the main surface (10). 20+30+15+10+0+10 = 85.
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.
Maintenance & community Scrapfly +67
Scrapfly 84
Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.
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.
Schema & documentation Scrapfly +60
Scrapfly 95
A Swagger reference per the 30 September check, and the MCP server exposes it as a web_scraping_openapi_specification resource. Every MCP tool has JSON Schema inputs generated from typed Go structs (25). llms.txt and Markdown twins such as pricing.md per the 30 September check. robots.txt still disallows /docs/llms.txt and the .md twins for crawlers it doesn't name, so they weren't re-read on 1 November (10). Descriptions say when to use a tool and when to switch, for example web_get_page falls back to web_scrape for tuning and to cloud_browser_open for interaction. A few are long and steer the model's next step (17 of 20). Typed inputs with enums, for example the vault service discriminator, and required fields (13 of 15). Error catalogue of 100+ ERR:: codes, each with HTTP status, retryable and billed flags and its own doc link (15). Dated release notes, newest 26 October 2026 (15). 25+10+17+13+15+15 = 95.
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.
Security & auth Scrapfly +57
Scrapfly 75
OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.
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.
Transparency & trust Scrapfly +32
Scrapfly 75
Closed service with terms updated 2026-09-30 under US law. SDKs are BSD 2-Clause, and the MCP source is public with no LICENSE file and ISC in package.json (15 of 30). Privacy policy updated 14 May 2026 with a published DPA and HIPAA BAA, but retention is as long as necessary, and the retention of scraped content isn't stated (18 of 30). Release notes date deprecations and removals, for example Scrapium v153 dropping legacy network interception on 11 September. No standing deprecation policy found (15 of 20). Stripe, Google Analytics, Google Ads and Google Cloud are named, with SCC and Data Privacy Framework transfers, but there's no full subprocessor list (10 of 20). The release notes still date each CDP removal, most recently Storage.getRelatedWebsiteSets in Scrapium v156 on 26 October. Not otherwise re-read on 1 November. 15+18+15+10 = 58.
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.
Payments & pricing Scrapfly +30
Scrapfly 60
No x402, MPP or L402 (0). Credit costs per request type (1 datacentre, 5 with rendering or Unblocker, 25 residential, 60 full-page screenshot) and plan prices are public. Unblocker surcharges per target aren't published, but cost_budget caps them (20). 1,000 free credits, no card, no time limit (20). A person signs up in a browser. OAuth still needs an account (0). Plan prices and the 1,000 free credits with no card re-read on the pricing page on 1 November. 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Score by category
| Category | Weight | Scrapfly | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 15 | Scrapfly +70 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 35 | Scrapfly +60 |
| Agent ergonomics | 13% | 80 | 59 | Scrapfly +21 |
| Security & auth | 14% | 75 | 18 | Scrapfly +57 |
| Payments & pricing | 10% | 60 | 30 | Scrapfly +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 17 | Scrapfly +67 |
| Transparency & trust | 7% | 75 | 43 | Scrapfly +32 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 77/100 | F 30.4/100 |
Facts side by side
| Fact | Scrapfly | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapfly (Joam Intelligence, LLC) | XCrawl |
| Hosted endpoint | https://api.scrapfly.io/scrape | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 62 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.scrapfly.mcp/mcp | not listed |
| Last release | 2026-10-15 | 2026-04-13 |
| Terms last updated | 2026-09-30 | no date given |
| Privacy policy last updated | 2026-05-14 | 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 | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 14 stars, 21k npm/wk | none |
| Agent reviews | 4/5 (2) | none |
How the scores have moved
Verdicts
Scrapfly
The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.
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
Scrapfly
- Send
X-Scrapfly-Api-Keyas a header rather thankey=so the key stays out of logs - Pass
unblocker=falseto the MCP web_scrape tool for plain pages, since it's on when omitted.aspis the deprecated alias - Set
cost_budgeton each scrape so an Unblocker upgrade can't blow through credits - Check
retryablein the error body before retrying, and stop onERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED - Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks
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, Scrapfly or XCrawl?
Scrapfly scores 77 (BB) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Scrapfly and XCrawl need an API key?
Scrapfly takes an API key or an OAuth sign-in. XCrawl needs an API key.
Can an agent call Scrapfly and XCrawl without installing anything?
Yes. Scrapfly has a hosted endpoint at https://api.scrapfly.io/scrape and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with Scrapfly or XCrawl
- Bright Data vs Scrapfly
- Bright Data vs XCrawl
- BrowserAct vs Scrapfly
- BrowserAct vs XCrawl
- Context.dev vs Scrapfly
- Context.dev vs XCrawl
- Crawl4AI vs Scrapfly
- Crawl4AI vs XCrawl
- fastCRW vs Scrapfly
- fastCRW vs XCrawl
- Decodo Web Data API vs Scrapfly
- Decodo Web Data API vs XCrawl
- Jina Reader vs Scrapfly
- Jina Reader vs XCrawl
- Microlink vs Scrapfly
- Microlink vs XCrawl
- Olostep vs Scrapfly
- Olostep vs XCrawl
- Outcrawl vs Scrapfly
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs Scrapfly
- Scrape.do vs XCrawl
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs XCrawl
- Scrapeless vs Scrapfly
- Scrapeless vs XCrawl
- ScraperAPI vs Scrapfly
- ScraperAPI vs XCrawl
- Scrapewise vs Scrapfly
- Scrapewise vs XCrawl
- Scrapfly vs ScrapingAnt
- Scrapfly vs ScrapingBee
- Scrapfly vs Scrapingdog
- Scrapfly vs Scrapling
- Scrapfly vs Spider
- Scrapfly vs WebScraping.AI
- Scrapfly vs ZenRows
- Scrapfly vs Zyte API
- 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 XCrawl
- Diffbot vs Scrapfly
- Diffbot vs XCrawl
- Nexscope vs Scrapfly
- Nexscope vs XCrawl
- Qovia vs Scrapfly
- Qovia vs XCrawl
- ScrapeAtlas vs Scrapfly
- ScrapeAtlas vs XCrawl
- Scrapfly vs SoldFetch
- SoldFetch vs XCrawl
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs XCrawl
- jevcrawl vs Scrapfly
- jevcrawl vs XCrawl
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/scrapfly-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapfly.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare scrapfly xcrawl(the CLI) - Over MCP
compare_tools {"a": "scrapfly", "b": "xcrawl"}at/mcp, no key