Head to head · Scraping · October 2026 research run
Oxylabs Web Scraper API vs XCrawl
Oxylabs Web Scraper API scores 65.4 (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 parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.
Ahead on
- Reliability, 75 against 15
- Schema & documentation, 68 against 35
- Agent ergonomics, 79 against 59
- Security & auth, 53 against 18
- Payments & pricing, 60 against 30
- Maintenance & community, 82 against 17
- Transparency & trust, 64 against 43
Watch for
Google's domain parameter was announced as gone on 18 March 2026 with no earlier changelog notice
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 Oxylabs Web Scraper API 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.
Maintenance & community Oxylabs Web Scraper API +65
Oxylabs Web Scraper API 82
The newest release is MCP server v0.10.2 on 29 October 2026, which changes how the client is reported in request headers, after v0.10.0 on 15 October added API-token sign-in (30). In the 90 days from 4 August, MCP releases v0.9.0 and v0.9.1 (10 August), v0.9.2 (14 August), v0.9.3 (7 September), v0.10.0 and v0.10.2, with v0.10.1 (28 October, dependency caps only) counted half, and four changelog entries tagged for this API (11, 17, 20 and 24 August) (20). Dated public changelog, support by email and round-the-clock live chat per the docs. GitHub issues were unread because github.com refused us (10 of 15). The MCP server is in the official registry as io.oxylabs/oxylabs-mcp, now at 0.10.2 (published 29 October), and official Python and Go SDKs exist (15). The MCP repository runs lint and test workflows. The Python SDK's last release is still 3.0.0 on 9 March 2026 and the Go SDK's 1.0.0 on 6 September 2024 (7 of 10).
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 Oxylabs Web Scraper API +60
Oxylabs Web Scraper API 75
Graded on the Web Scraper API (Classic) surface. Status page at uptime.oxylabs.io on incident.io with separate components for Scraper APIs Push-Pull and Real-Time (20). Its feed lists two incidents since 4 August 2026, a Datacenter Proxies outage on 13 August that doesn't touch this API and, on 26 October, 12 minutes (05:34 to 05:46 on the page's clock) on both Scraper API components and Web Unblocker. The page labels it a full outage, but its own text says users "may experience degraded performance, intermittent errors, or timeouts", so we read it as partial and minor (20 of 30). Job rates per plan are published, from 10 a second on the free trial to 100 on Business and Corporate, with rendered-job limits (15). 429 is not billed, responses carry x-ratelimit limit and remaining headers, and 612 and 613 faults can be retried at no cost. No Retry-After or backoff guidance was found for this API (10 of 15). No SLA is published. The General Conditions promise reasonable efforts (0). Generally available (10).
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.
Security & auth Oxylabs Web Scraper API +35
Oxylabs Web Scraper API 53
A username and password per product instance over HTTP Basic, with an editable password, optional IP whitelisting and several instances per account. The MCP server's v0.10.0 (15 October 2026) adds Web Scraper API tokens sent as a Bearer header, but the API docs still describe only the username and password, and no scopes were found (20 of 30). The Proxy Endpoint puts the pair in the proxy URL and needs TLS verification switched off, which we note without the query-string deduction. Scraping is read-only apart from POST requests to targets, callbacks and uploads to the customer's bucket, each instance can take a spending limit that disables it, and every MCP tool is marked read-only (10 of 20). No guidance on untrusted page content was found in the Web Scraper API docs, the MCP README or the agent skill (2 of 15). GET /v2/stats and the dashboard report usage by day and source, and jobs accept client notes. No per-request access log was found (7 of 15). ISO/IEC 27001:2022, SOC 2 Type 2 for Scraper API and yearly penetration tests per the trust centre (per the 8 October check, not re-read on 2 November). The disclosure programme is still paused except for critical issues sent to security@oxylabs.io, security.txt returns 404 and no bug bounty was found. That is above the 12 given for certification claims with no disclosure route (fireworks-inference, people-data-labs), because a route for critical issues and penetration tests are published (14 of 20).
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 Oxylabs Web Scraper API +33
Oxylabs Web Scraper API 68
No OpenAPI document was found. The contract is parameter tables per source plus a Postman collection, and the MCP server types every input (10 of 25). llms.txt indexes the docs and every page is served as Markdown by adding .md (10). Each source page states its parameters and defaults, and the MCP output_format description says when to choose links, Markdown or HTML, though tool descriptions are two lines (13 of 20). MCP inputs use enumerations for rendering, user agent and output format. The REST API takes context as a list of key and value pairs and free-form parsing instructions (10 of 15). Request examples in several languages, sample outputs, and a response code table covering HTTP, parser, storage and session codes (13 of 15). Paths are versioned at /v1 and the public changelog is dated, while the MCP repository's CHANGELOG.md stops at 0.2.2 in May 2025 although v0.10.2 shipped in October 2026 (12 of 15). llms.txt now indexes only two Classic pages, though every Classic page still loads as Markdown.
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 Oxylabs Web Scraper API +30
Oxylabs Web Scraper API 60
No x402, MPP or L402 (0). Per-1,000-result prices by target and plan are public, now on the Web API /Scrape pricing page that the old Web Scraper API pricing URL redirects to, at the same Starter rates (20). A one-time $5 welcome credit needs no payment details (20). A person registers in the dashboard and creates the product instance (0). The Classic overview page still says to contact the team for credentials, so the trial route for this surface is unconfirmed. 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.
Transparency & trust Oxylabs Web Scraper API +21
Oxylabs Web Scraper API 64
Closed service under public General Conditions naming oxylabs, UAB of Vilnius, still last updated 5 October 2026, with MIT clients (15 of 30). The privacy policy was last reviewed on 22 October 2026 and still doesn't name the controller or say anything about scraped content. Clause 4.3.9 of the General Conditions lets Oxylabs keep data gathered through Web API and Web Unblocker and use it at its discretion, and it is unclear whether Web API there includes this Classic API. A DPA is published and Push-Pull results are kept for at least 24 hours (14 of 30). No deprecation policy. Removals appear in the changelog on the day they take effect, and the General Conditions give 14 days' notice of contract changes (6 of 20). The DPA says the sub-processor list is available on request. The privacy policy names some vendors, and data locations are given only as the EEA and the US (7 of 20).
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.
Score by category
| Category | Weight | Oxylabs Web Scraper API | XCrawl | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 15 | Oxylabs Web Scraper API +60 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 35 | Oxylabs Web Scraper API +33 |
| Agent ergonomics | 13% | 79 | 59 | Oxylabs Web Scraper API +20 |
| Security & auth | 14% | 53 | 18 | Oxylabs Web Scraper API +35 |
| Payments & pricing | 10% | 60 | 30 | Oxylabs Web Scraper API +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 17 | Oxylabs Web Scraper API +65 |
| Transparency & trust | 7% | 64 | 43 | Oxylabs Web Scraper API +21 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 65.4/100 | F 30.4/100 |
Facts side by side
| Fact | Oxylabs Web Scraper API | XCrawl |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | oxylabs, UAB | XCrawl |
| Hosted endpoint | https://realtime.oxylabs.io/v1/queries | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT | none |
| Tools exposed | 10 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.oxylabs/oxylabs-mcp | not listed |
| Last release | 2026-10-29 | 2026-04-13 |
| Terms last updated | 2026-10-05 | no date given |
| Privacy policy last updated | 2024-10-14 | no date given |
| Customer content may train models | yes | 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 | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 18k PyPI/wk | none |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
XCrawl
No score change since it was listed.
Verdicts
Oxylabs Web Scraper API
Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools, released twice in late October 2026. Since Web API launched on 7 October the docs call it Classic and send new users to sales for credentials, Google's domain parameter was removed with notice only on the day, and no OpenAPI document was found.
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
Oxylabs Web Scraper API
- Send
"markdown": truefor page reading. HTML is the default output and costs far more tokens - Add
"render": "html"only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan - Treat 612 and 613 as retryable at no charge, and read the
x-ratelimit-*-remainingheaders before raising concurrency - Use
geo_locationfor Google localisation. Thedomainparameter was removed in March 2026 - Pin
oxylabs-mcpto 0.10.1 or later. Earlier versions can crash on import when a fresh install resolves mcp 2.x
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, Oxylabs Web Scraper API or XCrawl?
Oxylabs Web Scraper API scores 65.4 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do Oxylabs Web Scraper API and XCrawl need an API key?
Both need an API key.
Can an agent call Oxylabs Web Scraper API and XCrawl without installing anything?
Yes. Oxylabs Web Scraper API has a hosted endpoint at https://realtime.oxylabs.io/v1/queries and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.
Other comparisons with Oxylabs Web Scraper API or XCrawl
- Apify MCP Server vs Oxylabs Web Scraper API
- Bright Data vs Oxylabs Web Scraper API
- Bright Data vs XCrawl
- BrowserAct vs Oxylabs Web Scraper API
- BrowserAct vs XCrawl
- Context.dev vs Oxylabs Web Scraper API
- Context.dev vs XCrawl
- Crawl4AI vs Oxylabs Web Scraper API
- Crawl4AI vs XCrawl
- fastCRW vs Oxylabs Web Scraper API
- fastCRW vs XCrawl
- Decodo Web Data API vs Oxylabs Web Scraper API
- Decodo Web Data API vs XCrawl
- jevcrawl vs Oxylabs Web Scraper API
- Jina Reader vs Oxylabs Web Scraper API
- Jina Reader vs XCrawl
- Microlink vs Oxylabs Web Scraper API
- Microlink vs XCrawl
- Olostep vs Oxylabs Web Scraper API
- Olostep vs XCrawl
- Outcrawl vs Oxylabs Web Scraper API
- Outcrawl vs XCrawl
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs ScrapeOps Proxy API Aggregator
- Oxylabs Web Scraper API vs ScraperAPI
- Oxylabs Web Scraper API vs Scrapewise
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs ScrapingAnt
- Oxylabs Web Scraper API vs ScrapingBee
- Oxylabs Web Scraper API vs Scrapingdog
- Oxylabs Web Scraper API vs Scrapling
- Oxylabs Web Scraper API vs Spider
- Oxylabs Web Scraper API vs WebScraping.AI
- Oxylabs Web Scraper API vs ZenRows
- Oxylabs Web Scraper API vs Zyte API
- 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
- Firecrawl MCP vs XCrawl
- Diffbot vs Oxylabs Web Scraper API
- Diffbot vs XCrawl
- Firecrawl MCP vs Oxylabs Web Scraper API
- Nexscope vs Oxylabs Web Scraper API
- Nexscope vs XCrawl
- Oxylabs Web Scraper API vs Qovia
- Oxylabs Web Scraper API vs ScrapeAtlas
- Oxylabs Web Scraper API vs SoldFetch
- Qovia vs XCrawl
- ScrapeAtlas vs XCrawl
- SoldFetch vs XCrawl
- Apify MCP Server vs XCrawl
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs XCrawl
Machine-readable
- This page as Markdown
/compare/oxylabs-web-scraper-vs-xcrawl.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/oxylabs-web-scraper.json·/api/v1/tools/xcrawl.json - From a terminal
anchor compare oxylabs-web-scraper xcrawl(the CLI) - Over MCP
compare_tools {"a": "oxylabs-web-scraper", "b": "xcrawl"}at/mcp, no key