Head to head · Scraping · October 2026 research run
Scrapingdog vs XCrawl
Scrapingdog scores 40.3 (E) on agent readiness against XCrawl's 30.4 (F), and leads in 5 of 7 scored categories. XCrawl leads on agent ergonomics and security & auth. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons
Which one, for what
Best for A budget agent that wants parsed Google, Amazon or LinkedIn results and can keep the key out of logs.
Ahead on
- Reliability, 49 against 15
- Schema & documentation, 53 against 35
- Payments & pricing, 60 against 30
- Maintenance & community, 25 against 17
- Transparency & trust, 56 against 43
Watch for
The REST API takes the key only in the URL query string
XCrawl F
Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.
Ahead on
- Agent ergonomics, 59 against 52
- Security & auth, 18 against 5
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 Scrapingdog +34
Scrapingdog 49
The footer still links an UptimeRobot status page. Its monitors load only from UptimeRobot's /api/ path, which robots.txt disallows, and the page itself shows "Loading..." and a fetch error, so no component could be read (0 of 20). No readable incident history (5). Concurrency per plan is published, 1 on Free up to 2,200 on the top plan, and over the limit returns 429 (15). The agent onboarding guide linked from llms.txt says to retry 410, 429 and occasional 400s with backoff, not to retry 401 or 403, and that failed requests aren't charged; requests time out after 60 seconds. No Retry-After or idempotency keys (12 of 15). A public SLA page says Scrapingdog aims for 99 per cent monthly uptime and compensates downtime in credits, with no measurement method or date, per the 1 October check, not re-read on 10 November (7 of 10, the earlier partial held). Generally available (10). Total 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.
Payments & pricing Scrapingdog +30
Scrapingdog 60
No x402, MPP or L402 (0). Credit costs per API and plan prices are public, from 1 credit for a rotating-proxy request to 100 for a LinkedIn profile (20). Free plan of 100 credits and 1 concurrent request, no card; the docs say 200 requests a month (20). The agent onboarding guide says there is no device-code or browser-callback flow and a person signs up and copies the key from the dashboard (0). Total 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.
Schema & documentation Scrapingdog +18
Scrapingdog 53
No OpenAPI spec found. The MCP builds typed zod inputs for 35 tools from a declarative registry, and ai_extract_rules is a JSON string (12 of 25). llms.txt at the site root, re-read on 10 November, links the docs and a Markdown onboarding guide for agents (10). MCP descriptions say what each endpoint does but not when to avoid it, and the web_scrape tool tells the model the API default for dynamic is false while the docs say rendering is on by default (10 of 20). Booleans, numbers and strings with few enums, plus the JSON-string field (9 of 15). Code examples on each docs page and 8 documented status codes (12 of 15). No changelog and no versioned API paths found (0). Total 53; the score published on 1 October was 43, ten below these lines, and is corrected to their sum.
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 XCrawl +13
Scrapingdog 5
One account key with no scopes, and we found no rotation or revocation docs; team members get their own keys (10). The REST API takes the key only in the api_key query string, with no header option, so less 10 (0 of 30). The hosted MCP server takes the key as a bearer header, then passes it to the API in the query string. No read-only mode or least-privilege key. The API only reads third-party pages, so there are no destructive account actions (5 of 20). No prompt-injection guidance in the docs, the onboarding guide or the MCP README (0 of 15). No request log or per-call audit found; /account reports credits and concurrency only (0 of 15). No security.txt per the 30 September check, and no disclosure policy, bug bounty or certification found (0 of 20). Total 5.
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 Scrapingdog +13
Scrapingdog 56
Closed service with terms revised 13 January 2026 (re-read 10 November), naming OpenData Labs Private Limited under the laws of Rajasthan, India, with no postal address. The MCP is MIT (15 of 30). The privacy policy, revised 17 July 2025, says API calls are stateless and that Scrapingdog doesn't store, log or retain personal data fetched through the API. A DPA is published. No retention periods for account data, per the 1 October check, not re-read on 10 November (22 of 30). No deprecation policy or dated notices found (0). No processors or data locations named (0 of 20). Total 37.
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.
Maintenance & community Scrapingdog +8
Scrapingdog 25
The newest dated releases are the SDKs and MCP server first published on 31 July and 1 August 2026, 102 days ago; no API changelog or later dated release found. The MCP repository became a hosted service at mcp.scrapingdog.com in commits of 25 and 26 October with no version bump, tag or changelog entry, so not a release (10 of 30). Nothing dated in the 90 days from 12 August (0 of 20). We couldn't read GitHub issues. The MCP repository has 13 commits, the last seven on 25 and 26 October, and support is by chat and email (5 of 25). Node and Python SDKs, current per the 1 October check; npm and PyPI weren't readable on 10 November (8 of 15). The MCP repository now runs typecheck, build and a smoke suite in CI before each deploy, with no tags or readable run results (2 of 10, the earlier partial held). Total 25.
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.
Score by category
| Category | Weight | Scrapingdog | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 15 | Scrapingdog +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 35 | Scrapingdog +18 |
| Agent ergonomics | 13% | 52 | 59 | XCrawl +7 |
| Security & auth | 14% | 5 | 18 | XCrawl +13 |
| Payments & pricing | 10% | 60 | 30 | Scrapingdog +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 17 | Scrapingdog +8 |
| Transparency & trust | 7% | 56 | 43 | Scrapingdog +13 |
| Negative events | ≤15 | -2 | 0 | |
| Total | E 40.3/100 | F 30.4/100 |
Facts side by side
| Fact | Scrapingdog | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapingdog (OpenData Labs) | XCrawl |
| Hosted endpoint | https://api.scrapingdog.com/scrape | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 35 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.Darshan972/scrapingdog-mcp | not listed |
| Last release | 2026-07-31 | 2026-04-13 |
| Terms last updated | 2026-01-13 | no date given |
| Privacy policy last updated | 2025-07-17 | 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 |
| Popularity | 0 stars | none |
| Agent reviews | 3/5 (2) | none |
How the scores have moved
Verdicts
Scrapingdog
A plain request is 1 credit, about $0.20 per 1,000 on Lite, and failed requests aren't charged. The REST API takes its key only in the URL query string, and the MCP server describes JavaScript rendering as off by default when the API turns it on at 5 credits.
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
Scrapingdog
- Add dynamic=false unless the page needs JavaScript. It cuts the cost from 5 credits to 1, whatever the MCP description says
- Connect the hosted MCP with the key as a bearer header, and keep REST request URLs out of logs, since they carry api_key
- Set client timeouts above 60 seconds and retry 410 and 429 with backoff. Failures aren't billed
- Prefer the parsed endpoints (Google, Amazon) over scraping the raw page when one exists
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, Scrapingdog or XCrawl?
Scrapingdog scores 40.3 (E) on agent readiness against XCrawl's 30.4 (F), and leads in 5 of 7 scored categories. XCrawl leads on agent ergonomics and security & auth.
Do Scrapingdog and XCrawl need an API key?
Both need an API key.
Can an agent call Scrapingdog and XCrawl without installing anything?
Yes. Scrapingdog has a hosted endpoint at https://api.scrapingdog.com/scrape and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with Scrapingdog or XCrawl
- Apify MCP Server vs Scrapingdog
- Bright Data vs Scrapingdog
- Bright Data vs XCrawl
- BrowserAct vs Scrapingdog
- BrowserAct vs XCrawl
- Context.dev vs Scrapingdog
- Context.dev vs XCrawl
- Crawl4AI vs Scrapingdog
- Crawl4AI vs XCrawl
- fastCRW vs Scrapingdog
- fastCRW vs XCrawl
- Decodo Web Data API vs Scrapingdog
- Decodo Web Data API vs XCrawl
- jevcrawl vs Scrapingdog
- Jina Reader vs Scrapingdog
- Jina Reader vs XCrawl
- Microlink vs Scrapingdog
- Microlink vs XCrawl
- Olostep vs Scrapingdog
- Olostep vs XCrawl
- Outcrawl vs Scrapingdog
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs Scrapingdog
- Oxylabs Web Scraper API vs XCrawl
- Scrape.do vs Scrapingdog
- Scrape.do vs XCrawl
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs XCrawl
- Scrapeless vs Scrapingdog
- Scrapeless vs XCrawl
- ScraperAPI vs Scrapingdog
- ScraperAPI vs XCrawl
- Scrapewise vs Scrapingdog
- Scrapewise vs XCrawl
- Scrapfly vs Scrapingdog
- Scrapfly vs XCrawl
- ScrapingAnt vs Scrapingdog
- ScrapingAnt vs XCrawl
- ScrapingBee vs Scrapingdog
- ScrapingBee vs XCrawl
- Scrapingdog vs Scrapling
- Scrapingdog vs Spider
- Scrapingdog vs WebScraping.AI
- Scrapingdog vs ZenRows
- Scrapingdog vs Zyte API
- Scrapling vs XCrawl
- Spider vs XCrawl
- WebScraping.AI vs XCrawl
- XCrawl vs ZenRows
- XCrawl vs Zyte API
- Firecrawl MCP vs Scrapingdog
- Firecrawl MCP vs XCrawl
- Diffbot vs Scrapingdog
- Diffbot vs XCrawl
- Nexscope vs Scrapingdog
- Nexscope vs XCrawl
- Qovia vs Scrapingdog
- Qovia vs XCrawl
- ScrapeAtlas vs Scrapingdog
- ScrapeAtlas vs XCrawl
- Scrapingdog vs SoldFetch
- SoldFetch vs XCrawl
- Apify MCP Server vs XCrawl
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs Scrapingdog
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/scrapingdog-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapingdog.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare scrapingdog xcrawl(the CLI) - Over MCP
compare_tools {"a": "scrapingdog", "b": "xcrawl"}at/mcp, no key