Head to head · Scraping · October 2026 research run
XCrawl vs Zyte API
Zyte API scores 72.2 (BB) 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
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
Watch for
Xcrawl LLC is named with no state, registration number or address, and the terms name no governing law
Zyte API BB
Best for An agent or pipeline that fetches protected pages and wants the service to choose proxy and browser per site and to bill only success, and teams already on Scrapy.
Ahead on
- Reliability, 85 against 15
- Schema & documentation, 85 against 35
- Agent ergonomics, 72 against 59
- Security & auth, 55 against 18
- Payments & pricing, 60 against 30
- Maintenance & community, 77 against 17
- Transparency & trust, 67 against 43
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Request price depends on the target site's tier, from $0.13 to $1.27 per 1,000 HTTP requests and $1.01 to $16.08 with a browser on pay-as-you-go
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 Zyte API +70
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.
Zyte API 85
Graded as a hosted API. status.zyte.com runs on Atlassian Statuspage with ten components and incident history (20). In the 90 days to 1 November 2026 its history feed lists two Zyte API incidents, both degraded browser rendering with higher latency and 520 errors, on 10 to 11 September and 13 September, neither marked as an outage, and three incidents outside the API, Scrapy Cloud periodic jobs on 17 August and the web dashboard and Scrapy Cloud periodic jobs down from 28 to 30 October, which Zyte says affected no other product. All partial, so minor (20 of 30). Rate limits are published as 3,000 requests a minute per key on standard plans and a custom limit on Enterprise, though per-site limits aren't (15). 429, 503 and 520 carry Retry-After, and the docs give a backoff table and say which responses to retry, per the 9 October check (15). Enterprise plans list service level agreements for support response times. No uptime SLA is published (5 of 10). Zyte API is generally available, and Zyte MCP carries no beta label on 1 November (10).
Maintenance & community Zyte API +60
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.
Zyte API 77
The Agentic Web Data plugin (zytedata/skills) released 0.4.1 on 26 October 2026, 6 days before 1 November (30). Every dated source counted. In the 90 days from 3 August the plugin released 0.3.0, 0.3.1, 0.4.0 and 0.4.1 (17 and 22 September, 5 and 26 October) and scrapy-zyte-api 0.36.0 on 20 August. python-zyte-api 0.11.0 of 23 July has left the window, and its main branch holds unreleased work since (a CVE floor for brotli, Python 3.15 support), with no release by 1 November (20). There is no public API changelog. Support runs through tickets and a Discord server, and we did not read GitHub issues (8 of 15 for a closed service). python-zyte-api 0.11.0 is current, with Python 3.10 or later, and covers one language. The official MCP registry lists only a third-party Zyte entry (io.github.pipeworx-io/zyte), none from Zyte (12 of 15). The client repository has test and publish workflows and merged dependency updates on 20 and 26 October 2026. We did not see CI results (7 of 10).
Schema & documentation Zyte API +50
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.
Zyte API 85
The reference prints an OpenAPI 3.0.3 document for POST /v1/extract, though the Search API's /v1/search is documented in tables outside it (25). docs.zyte.com has an llms.txt and Markdown twins of its pages (10). The operation description states which output fields can be combined and which can't, and field descriptions give defaults (17 of 20). Inputs are typed, with 51 enums and required fields marked. customAttributes takes a free-form schema (13 of 15). The spec has a dozen request examples, and each error status has a problem+json example (15). The path is versioned /v1 and the spec says 1.0.0, but we found no dated changelog for the API in the docs sitemap of 150 pages (5 of 15).
Security & auth Zyte API +37
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.
Zyte API 55
API keys are revocable, an organisation can hold several, and none travels in a URL. Keys carry no permission scopes. Zyte MCP signs in over OAuth and works through its own key, mcp_access_key (22 of 30). An owner can set a blocking spending limit per key. We found no read-only mode, and the MCP docs warn that the agent can delete schedules and collections with no undo, leaving approval to the MCP client (8 of 20). The API returns untrusted web content, and the only guidance found is to review what the agent asks to do (2 of 15). The Stats API and dashboard break usage down by key, domain and request type, requests can be tagged, and each response has a request-id. No per-request log for the operator was found (10 of 15). ISO 27001 certification per the trust centre, a responsible disclosure programme with a hall of fame and no rewards, penetration test reports under NDA, and no security.txt (www.zyte.com/.well-known/security.txt answered 404 on 1 November) (13 of 20).
Payments & pricing Zyte API +30
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.
Zyte API 60
The official Python client documents x402 against api-x402.zyte.com, but our one unauthenticated request there on 1 November 2026, as on 9 October, returned 401 /auth/not-valid with WWW-Authenticate: Basic and no 402 challenge, and the main docs and pricing page don't mention it, so we score the line as not established (0 of 40). Per-1,000 prices for all five site tiers, screenshots and extraction are public, though a given site's tier needs the dashboard's cost estimator (20). $5 of credit for the first billing month on standard plans ($200 on Enterprise), with no card per the site, re-read in the pricing docs on 1 November (20). A person signs up in a browser, and the MCP route needs a browser sign-in too (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Zyte API +24
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.
Zyte API 67
A closed service with terms last updated on 22 September 2026 (unchanged on 1 November) that name Zyte Group Limited and contain a Zyte API section. The Python client is BSD 3-Clause (15 of 30). The privacy policy (30 August 2024), a DPA and a sub-processor list are public, with retention stated for support tickets (4 years) and invoices (7 years). Retention of request data and scraped content isn't stated, and the terms let Zyte use Service Data for product development and product training (17 of 30). Site tier changes get two weeks' notice and the Smart Proxy Manager retirement was announced with a date, but there is no standing API deprecation policy and the terms allow changes with or without notice (10 of 20). The sub-processor list names 36 companies with addresses and purposes, and the privacy policy names the United States and Ireland as processing locations (16 of 20).
Score by category
| Category | Weight | XCrawl | Zyte API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 15 | 85 | Zyte API +70 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 35 | 85 | Zyte API +50 |
| Agent ergonomics | 13% | 59 | 72 | Zyte API +13 |
| Security & auth | 14% | 18 | 55 | Zyte API +37 |
| Payments & pricing | 10% | 30 | 60 | Zyte API +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 17 | 77 | Zyte API +60 |
| Transparency & trust | 7% | 43 | 67 | Zyte API +24 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 30.4/100 | BB 72.2/100 |
Facts side by side
| Fact | XCrawl | Zyte API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | XCrawl | Zyte Group Limited |
| Hosted endpoint | https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp | https://api.zyte.com/v1/extract |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | Proprietary service under Zyte's terms of service. The Python client is BSD 3-Clause, and the Agentic Web Data plugin is under Zyte's own end-user licence |
| Tools exposed | 7 | 34 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-04-13 | 2026-10-26 |
| Terms last updated | no date given | 2026-09-22 |
| Privacy policy last updated | no date given | 2024-08-30 |
| Customer content may train models | not found in the text | yes |
| 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 | yes |
| Popularity | none | 42k PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |
How the scores have moved
XCrawl
No score change since it was listed.
Verdicts
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.
Zyte API
One POST endpoint with an OpenAPI 3 contract picks proxies, browser rendering and extraction per site, bills only successful responses, and sends problem+json errors with Retry-After. Prices vary by target site across five tiers, no dated API changelog was found, and the Python client's raised brotli floor for CVE-2026-111497, a flaw in brotli, is merged but unreleased.
Before you call either
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
Zyte API
- Send the API key as the Basic auth username with an empty password to
https://api.zyte.com/v1/extract. Set only one ofhttpResponseBodyorbrowserHtml, or one extraction field - Ask for
httpResponseBodybeforebrowserHtml. Browser requests cost about eight to thirteen times more per tier - Retry 429, 503 and 520 after the
Retry-Afterseconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451 - Read
statusCodein a 200 response. A target site's 404 comes back as a successful, billed Zyte API response - Have the owner set a blocking spending limit on the key you use. A 403
/auth/account-suspendedmeans the limit or the trial month ended
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Retrieve and decode HTML with Zyte, for Zyte API
Questions
Which is better for AI agents, XCrawl or Zyte API?
Zyte API scores 72.2 (BB) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.
Do XCrawl and Zyte API need an API key?
XCrawl needs an API key. Zyte API takes an API key or an OAuth sign-in.
Can an agent call XCrawl and Zyte API without installing anything?
Yes. XCrawl has a hosted endpoint at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp and Zyte API at https://api.zyte.com/v1/extract.
Other comparisons with XCrawl or Zyte API
- Apify MCP Server vs Zyte API
- Bright Data vs XCrawl
- Bright Data vs Zyte API
- BrowserAct vs XCrawl
- BrowserAct vs Zyte API
- Context.dev vs XCrawl
- Context.dev vs Zyte API
- Crawl4AI vs XCrawl
- Crawl4AI vs Zyte API
- fastCRW vs XCrawl
- fastCRW vs Zyte API
- Decodo Web Data API vs XCrawl
- Decodo Web Data API vs Zyte API
- jevcrawl vs Zyte API
- Jina Reader vs XCrawl
- Jina Reader vs Zyte API
- Microlink vs XCrawl
- Microlink vs Zyte API
- Olostep vs XCrawl
- Olostep vs Zyte API
- Outcrawl vs XCrawl
- Outcrawl vs Zyte API
- Oxylabs Web Scraper API vs XCrawl
- Oxylabs Web Scraper API vs Zyte API
- Scrape.do vs XCrawl
- Scrape.do vs Zyte API
- ScrapeGraphAI vs XCrawl
- ScrapeGraphAI vs Zyte API
- Scrapeless vs XCrawl
- Scrapeless vs Zyte API
- ScraperAPI vs XCrawl
- ScraperAPI vs Zyte API
- Scrapewise vs XCrawl
- Scrapewise vs Zyte API
- Scrapfly vs XCrawl
- Scrapfly vs Zyte API
- ScrapingAnt vs XCrawl
- ScrapingAnt vs Zyte API
- ScrapingBee vs XCrawl
- ScrapingBee vs Zyte API
- Scrapingdog vs XCrawl
- Scrapingdog vs Zyte API
- Scrapling vs XCrawl
- Scrapling vs Zyte API
- Spider vs XCrawl
- Spider vs Zyte API
- WebScraping.AI vs XCrawl
- WebScraping.AI vs Zyte API
- XCrawl vs ZenRows
- ZenRows vs Zyte API
- Firecrawl MCP vs XCrawl
- Diffbot vs XCrawl
- Diffbot vs Zyte API
- Nexscope vs XCrawl
- Nexscope vs Zyte API
- Qovia vs XCrawl
- Qovia vs Zyte API
- ScrapeAtlas vs XCrawl
- ScrapeAtlas vs Zyte API
- SoldFetch vs XCrawl
- SoldFetch vs Zyte API
- Apify MCP Server vs XCrawl
- jevcrawl vs XCrawl
- ScrapeOps Proxy API Aggregator vs XCrawl
- ScrapeOps Proxy API Aggregator vs Zyte API
Machine-readable
- This page as Markdown
/compare/xcrawl-vs-zyte.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/xcrawl.json·/api/v1/tools/zyte.json - From a terminal
anchor compare xcrawl zyte(the CLI) - Over MCP
compare_tools {"a": "xcrawl", "b": "zyte"}at/mcp, no key