Head to head · Scraping · October 2026 research run
Bright Data vs XCrawl
Bright Data scores 59.4 (C) 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 Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.
Ahead on
- Reliability, 40 against 15
- Schema & documentation, 74 against 35
- Agent ergonomics, 79 against 59
- Security & auth, 69 against 18
- Payments & pricing, 60 against 30
- Maintenance & community, 87 against 17
- Transparency & trust, 61 against 43
Watch for
No public status page or incident history
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
- No incidents deducted, where Bright Data loses 6 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.
Maintenance & community Bright Data +70
Bright Data 87
MCP v4.3.0 on 2 November 2026 (30). Ten MCP releases since 6 August, 2.11.2 (11 September), 2.11.3 (15 September), 2.12.0 (8 October), 3.0.0 (11 October), 3.1.0 (15 October), 4.0.0 (18 October), 4.1.0 (20 October), 4.1.1 (29 October), 4.2.0 (1 November) and 4.3.0, and product release notes dated 19, 24 and 27 October (20). Issues not read (GitHub's pages refuse our reader); outside pull requests such as #200 were merged within a week, and the 1 October count of 13 open issues stands (12 of 25). io.github.brightdata/brightdata-mcp in the official registry under a GitHub-verified namespace, now at 4.3.0, the latest release (15). Tests run in CI on every push, and the release workflow runs the tests and npm audit signatures before publishing with provenance (10). 30+20+12+15+10 = 87.
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.
Security & auth Bright Data +51
Bright Data 69
API keys carry one of five roles (Admin, Finance, Ops, Limit, User), can be given an expiry, and are revoked or refreshed in the control panel, and the hosted MCP also takes OAuth 2.1 with PKCE and one mcp scope (30). The README's default hosted setup still puts the key in the URL as ?token=, a documented option, so less 10 (20). User-role keys can't change configuration, tools load by group, and tools carry readOnlyHint and destructiveHint, but browser tools can fill forms and click with no confirmation step from the server (14 of 20). Since 3.1.0 results from search, scrape, scraper, dataset and browser tools are wrapped as untrusted web content with a per-call marker, and since 2.12.0 a content gate, documented in the README and on by default, asks the user through MCP elicitation before returning page text that looks like instructions to change the MCP configuration (12 of 15). The MCP session_stats tool reports calls in a session. We didn't find a per-request log for operators (5 of 15). ISO 27001, 27017 and 27018, SOC 2 Type II under NDA, a public SOC 3, a managed private bug bounty and security fixes in the MCP changelog per the 1 October check. No security.txt (404 on 4 November). OSV holds no advisory for @brightdata/mcp (18 of 20). 20+14+12+5+18 = 69.
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.
Schema & documentation Bright Data +39
Bright Data 74
No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of run_scraper (14 of 20). Typed inputs with enums such as engine (bing or google), time_range and format (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, now dated to 27 October 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0, per the 1 October reading (10 of 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.
Payments & pricing Bright Data +30
Bright Data 60
No x402, MPP or L402. Issue #126 asks for x402 and is open (0). Web Unlocker and SERP at $1.50 per 1,000 successful requests, $1.30 on Scale, published without a login (20). 5,000 requests a month, 'No credit card required' (20). A person has to sign up and create a key in the control panel (0). 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.
Reliability Bright Data +25
Bright Data 40
No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). The SERP API fair-use page gives 1,000 requests a minute for unfunded accounts with HTTP 429 above it and a header that reads the account's limit, paid Web Unlocker plans state unlimited concurrency, and the free tier is 5,000 requests a month (15). The Web Unlocker error catalogue documents a 429 sr_rate_limit when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10). 0+5+15+10+0+10 = 40.
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.
Agent ergonomics Bright Data +20
Bright Data 79
Since MCP 3.1.0 (15 October 2026) all 32 tools are on by default, with groups= and tools= on the hosted URL or GROUPS and TOOLS locally to narrow them (5 for more than 30, plus 10 for the filters, 15). Markdown, text, HTML or JSON-LD output from the scrape tools, content cut at 200,000 characters, batch tools of up to 5 searches or 5 URLs and filterable dataset search, but no general field selection (15 of 20). Error codes with a retry-or-fix classification, and since 4.3.0 the local server uses the hosted server's codes (rate_limited, invalid_input, quota_exceeded) (17 of 20). Since 4.1.0 every tool sets readOnlyHint, destructiveHint and openWorldHint, with browser click and type marked destructive. Billing counts successful requests, and there are no idempotency keys (17 of 20, as firecrawl-mcp and apify-mcp). One required secret and auto-created zones, and official Python (brightdata-sdk) and JavaScript SDKs in the docs index (15). 15+15+17+17+15 = 79.
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 | Bright Data | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 15 | Bright Data +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 35 | Bright Data +39 |
| Agent ergonomics | 13% | 79 | 59 | Bright Data +20 |
| Security & auth | 14% | 69 | 18 | Bright Data +51 |
| Payments & pricing | 10% | 60 | 30 | Bright Data +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 17 | Bright Data +70 |
| Transparency & trust | 7% | 61 | 43 | Bright Data +18 |
| Negative events | ≤15 | -6 | 0 | |
| Total | C 59.4/100 | F 30.4/100 |
Facts side by side
| Fact | Bright Data | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bright Data | XCrawl |
| Hosted endpoint | https://api.brightdata.com/request | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 32 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.brightdata/brightdata-mcp | not listed |
| Last release | 2026-11-02 | 2026-04-13 |
| Terms last updated | 2026-06-16 | 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 | yes | not found in the text |
| Popularity | 2.6k stars | none |
| Agent reviews | 4/5 (2) | none |
How the scores have moved
Verdicts
Bright Data
Bright Data bills only successful requests, $1.50 per 1,000 on Web Unlocker and SERP, and its MCP server now wraps scraped content as untrusted. There's no public status page or incident history, and MCP 4.2.0 and 4.3.0 changed tool inputs and outputs in minor releases without notice.
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
Bright Data
- Connect with OAuth or keep the
?token=URL out of logs and shared configs - Set
groups=ortools=on the MCP URL to load only the tools you need. With neither, all 32 load - Send
countryandpageto the search tools from 4.3.0.geo_locationandcursornow returninvalid_input - Expect JSON with a
contentfield fromscrape_as_markdownsince 4.2.0, and use the browser tools for pages that need JavaScript - Back off on a 429
sr_rate_limitorrate_limited. Bright Data throttles a target whose success rate drops
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, Bright Data or XCrawl?
Bright Data scores 59.4 (C) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Bright Data and XCrawl need an API key?
Bright Data takes an API key or an OAuth sign-in. XCrawl needs an API key.
Can an agent call Bright Data and XCrawl without installing anything?
Yes. Bright Data has a hosted endpoint at https://api.brightdata.com/request and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with Bright Data or XCrawl
- Bright Data vs BrowserAct
- Bright Data vs Context.dev
- Bright Data vs Crawl4AI
- Bright Data vs fastCRW
- Bright Data vs Decodo Web Data API
- Bright Data vs Diffbot
- Bright Data vs jevcrawl
- Bright Data vs Jina Reader
- Bright Data vs Microlink
- Bright Data vs Olostep
- Bright Data vs Outcrawl
- Bright Data vs Oxylabs Web Scraper API
- Bright Data vs Scrape.do
- Bright Data vs ScrapeGraphAI
- Bright Data vs Scrapeless
- Bright Data vs ScrapeOps Proxy API Aggregator
- Bright Data vs ScraperAPI
- Bright Data vs Scrapewise
- Bright Data vs Scrapfly
- Bright Data vs ScrapingAnt
- Bright Data vs ScrapingBee
- Bright Data vs Scrapingdog
- Bright Data vs Scrapling
- Bright Data vs Spider
- Bright Data vs WebScraping.AI
- Bright Data vs ZenRows
- Bright Data vs Zyte API
- BrowserAct vs XCrawl
- Context.dev vs XCrawl
- Crawl4AI vs XCrawl
- fastCRW vs XCrawl
- Decodo Web Data API vs XCrawl
- 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
- Bright Data vs Firecrawl MCP
- Bright Data vs Qovia
- Firecrawl MCP vs XCrawl
- Diffbot vs XCrawl
- Nexscope vs XCrawl
- Qovia vs XCrawl
- ScrapeAtlas vs XCrawl
- SoldFetch vs XCrawl
- Apify MCP Server vs Bright Data
- Apify MCP Server vs XCrawl
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/bright-data-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bright-data.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare bright-data xcrawl(the CLI) - Over MCP
compare_tools {"a": "bright-data", "b": "xcrawl"}at/mcp, no key