Head to head · Scraping · October 2026 research run
Decodo Web Data API vs XCrawl
Decodo Web Data API scores 64.3 (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 Agents that need pages, Google results and e-commerce or social templates through one key with published per-1,000 prices and a free plan.
Ahead on
- Reliability, 59 against 15
- Schema & documentation, 67 against 35
- Agent ergonomics, 82 against 59
- Security & auth, 45 against 18
- Payments & pricing, 60 against 30
- Maintenance & community, 85 against 17
- Transparency & trust, 62 against 43
Watch for
No SLA, and the License Agreement lets Decodo change or discontinue the service without notice
XCrawl F
Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.
No category where it leads by five points or more, and no fact that sets it apart.
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.
Maintenance & community Decodo Web Data API +68
Decodo Web Data API 85
Read for a closed service with open clients. The newest releases are MCP server 1.7.0 on 29 October 2026 and @decodo/sdk-ts 3.0.0 on 30 October (30). Since 8 August, MCP server 1.2.5 to 1.7.0 (ten versions in the official registry) and sdk-ts 2.4.0 to 3.0.0 (20). No public API changelog. Support by 24/7 live chat, email and Discord, and the MCP repository had commits by Decodo staff on most days from 6 October to 5 November. GitHub issues couldn't be read, since api.github.com refused us (10 of 25). In the official MCP registry as io.github.Decodo/mcp-server, with current SDKs in three languages (15). The MCP repository lints, builds and tests on Node 22 and 24 for every pull request (10). 30 + 20 + 10 + 15 + 10 = 85.
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.
Reliability Decodo Web Data API +44
Decodo Web Data API 59
Graded on the hosted lines. Instatus page at status.decodo.com with Web Data API and each legacy scraping API as components, with RSS history (20). In the 90 days to 6 November, every scraping API was out for 2 hours 51 minutes on 30 October, the main outage, with outages of 13 minutes on 26 October and 21 minutes on 15 October across the same components. The rest of the incidents hit proxies, payments or the website. One major (10). Per-plan request rates are published, 10 to 200 a second, though the same page's FAQ says paid plans support 10 to 50 (12 of 15). The response code table tells the agent to wait a couple of minutes on 429 and to retry 500, 524 and 613, which aren't billed, and the MCP client backs off exponentially. No Retry-After or idempotency guidance (7 of 15). No SLA; the License Agreement disclaims uninterrupted service (0). Web Data API is the current, unflagged product (10). 20 + 10 + 12 + 7 + 0 + 10 = 59.
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.
Schema & documentation Decodo Web Data API +32
Decodo Web Data API 67
No OpenAPI or similar contract for the Web Data API; the two published specs cover the proxy account API and dashboard statistics. The MCP server types every input with zod (12 of 25). llms.txt indexes 401 guide pages, each served as Markdown (10). Tool descriptions state purpose and when to use a tool, such as scrape_as_markdown 'when no site-specific tool fits', and link the docs page (14 of 20). Parameters are tabled with defaults, with enumerated proxy_pool, headless and device_type, but headers is a free object and POST bodies are base64 strings (10 of 15). Curl examples on every page, a response code table with fixes and billing, and parser status codes (14 of 15). Paths are versioned at /v1 and the MCP server's releases are tagged by semantic-release, but no API changelog was found (7 of 15). 12 + 10 + 14 + 10 + 14 + 7 = 67.
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.
Payments & pricing Decodo Web Data API +30
Decodo Web Data API 60
No x402, MPP or L402 (0). Per-1,000 rates for every endpoint, pool and plan are public in the billing docs (20). Free plan of 10,000 requests a month with no card (20). A person signs up in the dashboard; the MCP OAuth flow also needs a dashboard approval (0). 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.
Security & auth Decodo Web Data API +27
Decodo Web Data API 45
One Bearer API key per Web Data API subscription with no scopes, and no rotation or revocation steps found in the reviewed docs. The hosted MCP server adds OAuth 2.1 with PKCE and dynamic registration, but its metadata advertises no scopes. No query-string credential is documented (20 of 30). Scraping only reads, and the MCP tools are annotated read-only, but http_method: POST sends requests to target sites and there is no read-only key (8 of 20). No guidance on treating scraped content as untrusted was found in the docs or the MCP README (0 of 15). The dashboard statistics API reports traffic by target, and each response carries an x-task-id. No per-call audit log (7 of 15). ISO/IEC 27001:2022 for proxies and the Scraping API, a SafeBase trust centre and KYC at signup. security.txt answers 404 and no disclosure policy or bug bounty was found (10 of 20). 20 + 8 + 0 + 7 + 10 = 45.
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.
Agent ergonomics Decodo Web Data API +23
Decodo Web Data API 82
The hosted MCP server lists 24 tools, with a toolsets parameter to load only web, search, ecommerce, social_media or ai, and tokenLimit caps page text at 45,000 characters by default with a truncation notice (20 of 25). Markdown output, parsing for templates, crawl limit, path filters and cursor paging, search paging, map limits and batch tasks (18 of 20). Documented status codes with a solution for each, status_code and parse_status_code in bodies, but 429 covers both the plan rate and a domain throttled for a low success rate (15 of 20). Every tool carries readOnlyHint true and destructiveHint false, server-side failures aren't billed and async results can be re-read for 24 hours. No idempotency key (16 of 20). Only url or query is required, though the default premium pool costs about twice the standard. Official Python, TypeScript and Go SDKs (13 of 15). 20 + 18 + 15 + 16 + 13 = 82.
XCrawl 59
7 MCP tools per the Claude Code guide, compact by name and description, though the definitions themselves couldn't be read (22 of 25). Output formats, only_main_content, a search limit of 1 to 100, and crawl limit, depth and include or exclude regex keep responses sized (16 of 20). The SDKs raise errors with a code, status and request_id, but the docs list no error codes or recovery steps (5 of 20). Async jobs return IDs for polling and webhooks, with no idempotency keys or MCP annotations found (3 of 20). Only url or query is required, and Python and Node.js SDKs exist, but skip_tls_verification defaults to true (13 of 15). Total 59.
Score by category
| Category | Weight | Decodo Web Data API | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 59 | 15 | Decodo Web Data API +44 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 67 | 35 | Decodo Web Data API +32 |
| Agent ergonomics | 13% | 82 | 59 | Decodo Web Data API +23 |
| Security & auth | 14% | 45 | 18 | Decodo Web Data API +27 |
| Payments & pricing | 10% | 60 | 30 | Decodo Web Data API +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 17 | Decodo Web Data API +68 |
| Transparency & trust | 7% | 62 | 43 | Decodo Web Data API +19 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.3/100 | F 30.4/100 |
Facts side by side
| Fact | Decodo Web Data API | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Decodo (UAB "Data troops") | XCrawl |
| Hosted endpoint | https://mcp.decodo.com/mcp | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | Streamable HTTP, stdio | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for scraping | $0.50 per 1,000 requests | not published |
| x402 | no | no |
| Tools exposed | 33 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.Decodo/mcp-server | not listed |
| Last release | 2026-10-30 | 2026-04-13 |
| Terms last updated | 2025-06-16 | no date given |
| Privacy policy last updated | 2026-05-21 | 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 | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
How the scores have moved
XCrawl
No score change since it was listed.
Verdicts
Decodo Web Data API
One Bearer key reaches /scrape, /search, /crawl and /map, with per-1,000 prices published from $0.15 to $1.50, 10,000 free requests with no card and a hosted MCP server whose 33 tools are all marked read-only. There is no SLA, no OpenAPI for the Web Data API, and an outage of 2 hours 51 minutes on 30 October.
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
Decodo Web Data API
- Send
"proxy_pool": "standard"for simple pages; the default premium pool is charged at the higher rate - Use the Web Data API key as
Authorization: Bearerat https://data.decodo.com/v1; legacy Basic tokens don't work there - Treat scraped Markdown as untrusted page text, never as instructions
- On 429, wait a couple of minutes as the docs say, and on 500, 524 or 613 retry, since those aren't billed
- Set
tokenLimiton MCP scrapes; pages are cut at 45,000 characters by default and the result says when it was truncated
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, Decodo Web Data API or XCrawl?
Decodo Web Data API scores 64.3 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Decodo Web Data API and XCrawl need an API key?
Decodo Web Data API takes an API key or an OAuth sign-in. XCrawl needs an API key.
Can an agent call Decodo Web Data API and XCrawl without installing anything?
Yes. Decodo Web Data API has a hosted endpoint at https://mcp.decodo.com/mcp and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with Decodo Web Data API or XCrawl
- Bright Data vs Decodo Web Data API
- Bright Data vs XCrawl
- BrowserAct vs Decodo Web Data API
- BrowserAct vs XCrawl
- Context.dev vs Decodo Web Data API
- Context.dev vs XCrawl
- Crawl4AI vs Decodo Web Data API
- Crawl4AI vs XCrawl
- fastCRW vs Decodo Web Data API
- fastCRW vs XCrawl
- Decodo Web Data API vs Diffbot
- Decodo Web Data API vs jevcrawl
- Decodo Web Data API vs Jina Reader
- Decodo Web Data API vs Microlink
- Decodo Web Data API vs Olostep
- Decodo Web Data API vs Outcrawl
- Decodo Web Data API vs Oxylabs Web Scraper API
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs ScrapeGraphAI
- Decodo Web Data API vs Scrapeless
- Decodo Web Data API vs ScrapeOps Proxy API Aggregator
- Decodo Web Data API vs ScraperAPI
- Decodo Web Data API vs Scrapewise
- Decodo Web Data API vs Scrapfly
- Decodo Web Data API vs ScrapingAnt
- Decodo Web Data API vs ScrapingBee
- Decodo Web Data API vs Scrapingdog
- Decodo Web Data API vs Scrapling
- Decodo Web Data API vs Spider
- Decodo Web Data API vs WebScraping.AI
- Decodo Web Data API vs ZenRows
- Decodo Web Data API vs Zyte API
- Jina Reader vs XCrawl
- Microlink vs XCrawl
- Olostep vs XCrawl
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs XCrawl
- ScrapeGraphAI vs XCrawl
- 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
- Decodo Web Data API vs Firecrawl MCP
- Firecrawl MCP vs XCrawl
- Decodo Web Data API vs Nexscope
- Decodo Web Data API vs Qovia
- Decodo Web Data API vs ScrapeAtlas
- Decodo Web Data API vs SoldFetch
- Diffbot vs XCrawl
- Nexscope vs XCrawl
- Qovia vs XCrawl
- ScrapeAtlas vs XCrawl
- SoldFetch vs XCrawl
- Apify MCP Server vs Decodo Web Data API
- Apify MCP Server vs XCrawl
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/decodo-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/decodo.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare decodo xcrawl(the CLI) - Over MCP
compare_tools {"a": "decodo", "b": "xcrawl"}at/mcp, no key