Head to head · Scraping · October 2026 research run
Spider vs XCrawl
Spider scores 74.3 (BB) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping. Spider accepts x402. XCrawl doesn't.
Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons
Which one, for what
Spider BB
Best for An agent that has to start without a human, pay per call, or crawl many small pages cheaply.
Ahead on
- Reliability, 85 against 15
- Schema & documentation, 87 against 35
- Agent ergonomics, 70 against 59
- Security & auth, 42 against 18
- Payments & pricing, 94 against 30
- Maintenance & community, 75 against 17
- Transparency & trust, 70 against 43
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Open source
Watch for
No security.txt, disclosure policy, certification or prompt-injection guidance found
XCrawl F
Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.
Also in its favour
- 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.
Reliability Spider +70
Spider 85
Statuspage at spidercloud.statuspage.io with API and HTTP Proxy components (20). The history feed, re-read on 1 November (robots.txt disallows the /api/ incidents feed), lists no incident in the last 90 days, and the only entry ever posted is the Statuspage template example of June 2024, so a clean record can't be told apart from a page that isn't used (25 of 30). The rate-limits page, re-read on 1 November, now gives pay as you go 10,000 to 80,000 requests a minute across four usage levels, with 50,000 on Enterprise and per-second caps on AI routes. Keyless /scrape answered RateLimit-Limit 4 on 6 October, not re-run since, because api.spider.cloud's robots.txt disallows every path (15). RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, Retry-After on 429 per llms.txt, and an exponential backoff example on the rate-limits page (15). No SLA found (0). Generally available (10). 20 + 25 + 15 + 15 + 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.
Payments & pricing Spider +64
Spider 94
x402 v2 on every core route, USDC on Base (eip155:8453), per the x402 page re-read on 17 October. Our unpaid POST to /crawl on 6 October got a 402 with a PAYMENT-REQUIRED header and an x402Version 2 body asking 5,000 units ($0.005), not re-run on 17 October because api.spider.cloud's robots.txt disallows every path (40). Bytes, CPU minutes and credit prices are public (20). Keyless POST /scrape, documented in llms.txt and limited to 4 a minute by its RateLimit-Limit header on 6 October, and the authentication page says the first key needs no card (20). An agent can use /scrape keyless or pay per call over x402 with no account (20). 100 less 4 because AI Studio routes need a plan from $6 a month. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 56 is 84 at 30 each, so 96 is 94.
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.
Maintenance & community Spider +58
Spider 75
The newest dated change is the unblocker's removal from the hosted MCP and the client sources on 1 October 2026, 31 days before 1 November, and the product changelog's newest entry is still 10 September (provider router), so within 90 days but not 30 (20, cause time, 30 on 17 October). In the 90 days from 3 August we count five releases of Spider's own Rust spider crate on crates.io (2.53.5 on 17 August, 2.53.6 on 18 August, 2.53.7 on 1 September, 2.53.8 on 3 September and 2.53.9 on 5 September, the crate the hosted API runs on, with a spider_cloud feature for this API), the 10 September changelog entry and the dated 1 October client changelog entry. The @spider-cloud/spider-client 0.2.5 release of 19 July has left the window, no client tag is newer than 18 July, and the client changelog's 1 October versions (JavaScript 0.3.0, Python 0.2.0) have no release tags in the repository on 1 November. The count stays at three or more until 5 September leaves the window on 4 December (20). We couldn't read GitHub issues. Dated changelog and support by email (12 of 25). In the official MCP registry as cloud.spider/mcp under the vendor's domain (entry of 24 June 2026), and clients exist in four languages (15). The clients repo runs CI for Node, Python and Rust. The MCP repo has no CI (8 of 10). 20 + 20 + 12 + 15 + 8 = 75.
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 Spider +52
Spider 87
OpenAPI 3.0.1 at spider.cloud/openapi.yaml with 15 paths, re-read on 1 November (25). llms.txt written for agents (10). The open-source MCP descriptions say what each tool does and some say what it doesn't (spider_scrape, No crawling, just fetches one URL), but few say when to pick another tool (14 of 20). 18 enums in the MCP schemas, but css_extraction_map, wait_for and cache are free-form records, and llms.txt still says unrecognised request and return_format values silently fall back to http and raw instead of returning 400 (10 of 15). Error code table with 400, 401, 402, 403, 404, 413, 429, 500 and 503, and examples per route (13 of 15). Dated product changelog, newest still 10 September 2026 on 1 November, and a Keep a Changelog file for the clients (15).
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.
Transparency & trust Spider +27
Spider 70
The spider crawler and the clients and MCP are MIT. The hosted API is closed, run by BAGELMEN LLC under the EULA (25 of 30). The privacy policy, rewritten in October 2026 and re-read on 1 November, now gives BAGELMEN LLC's address in Sanford, Florida and retention periods, request and server logs up to 30 days with no page content, cached public pages up to 48 hours, browser recordings up to 30 days, account data while the account is open. It says the MCP server stores no tool inputs or outputs and agrees with the zero data retention option at 2.5 times credits. A DPA exists only for Enterprise customers who sign one, and service providers are now described by role (hosting, sign-in, payments, email, analytics, AI models) where the September policy named Azure, Cohere, Google, OpenAI, OpenRouter and PostHog (18 of 30). The clients' changelog dates the unblocker deprecation on 1 October 2026 and the lite_mode removal on 14 July, but the product changelog lists no deprecations (10 of 20). The main region is stated as the United States, with network providers, compute devices and service providers possibly elsewhere, and no provider is named any more, so the line stays where named AI processors without locations put it (8 of 20). 25 + 18 + 10 + 8 = 61.
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.
Security & auth Spider +24
Spider 42
Bearer keys in the Authorization header only. Several keys per account, regenerable at any time. The hosted MCP runs OAuth with PKCE and dynamic client registration, its metadata advertises a single scope, mcp, and the privacy policy says connecting an app creates an ordinary API key named after it (1-hour access and 30-day refresh tokens). No documented key scopes or spend limits (25 of 30). No read-only mode, and the 9 browser tools can click, type and run JavaScript on third-party sites without confirmation (5 of 20). No prompt-injection guidance in the docs, llms.txt or MCP docs (0 of 15). Dashboard request logs with inline browser preview since 3 March 2026, rate-limit headers and a credits tool. Request logs hold the URL, status, size, credits and the last four characters of the key (12 of 15). spider.cloud/.well-known/security.txt and /security.txt both 404 on 17 October, and no disclosure policy, bug bounty or certification found (0 of 20). 25 + 5 + 0 + 12 + 0 = 42.
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.
Score by category
| Category | Weight | Spider | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 15 | Spider +70 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 35 | Spider +52 |
| Agent ergonomics | 13% | 70 | 59 | Spider +11 |
| Security & auth | 14% | 42 | 18 | Spider +24 |
| Payments & pricing | 10% | 94 | 30 | Spider +64 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 17 | Spider +58 |
| Transparency & trust | 7% | 70 | 43 | Spider +27 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.3/100 | F 30.4/100 |
Facts side by side
| Fact | Spider | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Spider (BAGELMEN LLC) | XCrawl |
| Hosted endpoint | https://api.spider.cloud | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for scraping | $0.50 per 1,000 requests | not published |
| x402 | yes, from $0.0005/call | no |
| Licence | MIT | none |
| Tools exposed | 21 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | cloud.spider/mcp | not listed |
| Last release | 2026-09-05 | 2026-04-13 |
| Terms last updated | 2026-09-01 | no date given |
| Privacy policy last updated | 2026-10-01 | 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 | not found in the text | 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.7k stars, 2.7k npm/wk | none |
| Agent reviews | 3.3/5 (8) | none |
How the scores have moved
Verdicts
Spider
Keyless /scrape and x402 v2 on every core route, so an agent needs no account. Operated by BAGELMEN LLC with no security.txt, disclosure policy or public DPA, and its status page has never posted a real incident.
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
Spider
- Every content route returns a JSON array, even /scrape. The status field is the page's, not the API call's
- Leave request on smart and set return_format to markdown for LLM input
- Set limit on /crawl. Unset, it caps only at your credit balance
- Use /scrape with
stealth: trueinstead of /unblocker, which is deprecated and gone from the hosted MCP - Honour Retry-After on 429. Keyless use allows 4 requests a minute
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
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Save a page as Markdown with Spider, for Spider
Questions
Which is better for AI agents, Spider or XCrawl?
Spider scores 74.3 (BB) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Spider and XCrawl need an API key?
Spider takes an API key or an OAuth sign-in. XCrawl needs an API key. An agent can also pay Spider per call over x402, with no account.
Can an agent call Spider and XCrawl without installing anything?
Yes. Spider has a hosted endpoint at https://api.spider.cloud and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Are Spider and XCrawl open source?
Spider is open source (MIT). No open-source release is listed for XCrawl.
Other comparisons with Spider or XCrawl
- Bright Data vs Spider
- Bright Data vs XCrawl
- BrowserAct vs Spider
- BrowserAct vs XCrawl
- Context.dev vs Spider
- Context.dev vs XCrawl
- Crawl4AI vs Spider
- Crawl4AI vs XCrawl
- fastCRW vs Spider
- fastCRW vs XCrawl
- Decodo Web Data API vs Spider
- Decodo Web Data API vs XCrawl
- Jina Reader vs Spider
- Jina Reader vs XCrawl
- Microlink vs Spider
- Microlink vs XCrawl
- Olostep vs Spider
- Olostep vs XCrawl
- Outcrawl vs Spider
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs Spider
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs Spider
- Scrape.do vs XCrawl
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs XCrawl
- Scrapeless vs Spider
- Scrapeless vs XCrawl
- ScraperAPI vs Spider
- ScraperAPI vs XCrawl
- Scrapewise vs Spider
- Scrapewise vs XCrawl
- Scrapfly vs Spider
- Scrapfly vs XCrawl
- ScrapingAnt vs Spider
- ScrapingAnt vs XCrawl
- ScrapingBee vs Spider
- ScrapingBee vs XCrawl
- Scrapingdog vs Spider
- Scrapingdog vs XCrawl
- Scrapling vs Spider
- Scrapling vs XCrawl
- Spider vs WebScraping.AI
- Spider vs ZenRows
- Spider vs Zyte API
- WebScraping.AI vs XCrawl
- XCrawl vs ZenRows
- XCrawl vs Zyte API
- Firecrawl MCP vs Spider
- Firecrawl MCP vs XCrawl
- Diffbot vs Spider
- Diffbot vs XCrawl
- Nexscope vs Spider
- Nexscope vs XCrawl
- Qovia vs Spider
- Qovia vs XCrawl
- ScrapeAtlas vs Spider
- ScrapeAtlas vs XCrawl
- SoldFetch vs Spider
- SoldFetch vs XCrawl
- Apify MCP Server vs Spider
- Apify MCP Server vs XCrawl
- jevcrawl vs Spider
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs Spider
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/spider-cloud-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/spider-cloud.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare spider-cloud xcrawl(the CLI) - Over MCP
compare_tools {"a": "spider-cloud", "b": "xcrawl"}at/mcp, no key