Head to head · Scraping · October 2026 research run

Scrapling vs Zyte API

Zyte API scores 72.2 (BB) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

Scrapling B

Best for Agents that need to fetch and drive pages locally, including JavaScript-heavy or bot-protected ones, without a hosted scraping bill.

Ahead on

  • Payments & pricing, 90 against 60
  • Maintenance & community, 93 against 77

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source

Watch for

Version 0.5.1 with a Beta classifier. v0.4.15, v0.5 and v0.5.1 each carried breaking changes, the last in a patch release

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 65
  • Security & auth, 55 against 39
  • Transparency & trust, 67 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card

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.

Payments & pricing Scrapling +30

Scrapling 90

Free, self-hosted software under BSD-3-Clause with nothing to buy, read with the self-hosted rule. No payment protocol (0), nothing to price (30), free (30), no signup or key (30). 0 + 30 + 30 + 30 = 90.

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.

Reliability Zyte API +20

Scrapling 65

Read on the local-software lines, since the MCP server runs on the user's machine over stdio or a self-run HTTP port. Installs from PyPI (scrapling[ai]) or Docker (pyd4vinci/scrapling, ghcr.io/d4vinci/scrapling), with Python 3.10 or later and 3.10 to 3.13 in the classifiers (20). tests.yml runs tox on Python 3.10 to 3.13 on macOS for pushes and pull requests to main and dev, and the repository holds about 1,390 test functions, 19 test files for the MCP tools among them. Run results on GitHub couldn't be read on 18 November, so passing on main is unchecked (15 of 25). Five issues were open on 18 November 2026 against 104,200 stars, the oldest from 24 October 2025, and two of them had a reply. The v0.5.1 notes credit fixes from outside contributors and close reported issues such as #540 (20 of 25). Breaking changes carry a warning and a migration guide in the changelog, but v0.5.1 broke remote browser connections in a patch release (10 of 15). Version 0.5.1 with a Development Status 4 Beta classifier (0). 20 + 15 + 20 + 10 + 0 = 65.

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).

Security & auth Zyte API +16

Scrapling 39

Read as local software with an optional HTTP transport. stdio needs no credential. Over HTTP the server refuses to start without a token or an explicit --no-auth, and accepts one shared bearer token with no scopes, rotated by restarting (15). Annotations let a client gate the destructive tools, and follow_redirects defaults to safe, which blocks redirects to private addresses. A direct request to localhost or a private address is not refused, and there is no read-only mode (10). Hidden elements, aria-hidden content, zero-width characters, comments and template tags are stripped by default before page text reaches the model, as documented in the MCP guide. The vendor's claim, untested by us (10). Browser sessions record network history the agent and operator can read back. No call log (4). No SECURITY.md, disclosure address or bug bounty in the repository, and GitHub's advisory page couldn't be read (0). 15 + 10 + 10 + 4 + 0 = 39.

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).

Maintenance & community Scrapling +16

Scrapling 93

v0.5.1 tagged and released on 4 November 2026, 14 days before 18 November (30). v0.4.15 (23 August), v0.5 (17 October in the changelog, tagged 18 October) and v0.5.1 (4 November), three in the 90 days (20). The v0.5.1 notes credit about a dozen pull requests from outside contributors. Five issues and 18 pull requests were open on 18 November, and the issue template points to GitHub Discussions and a Discord (20 of 25). The official MCP registry lists io.github.D4Vinci/Scrapling as active, with versions from 0.4.1 (27 February 2026) to 0.5.1 (4 November 2026) (15). Tests and code-quality workflows, PyPI trusted publishing, and current dependencies such as Playwright 1.62. Run results unread (8 of 10). 30 + 20 + 20 + 15 + 8 = 93.

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).

Transparency & trust Zyte API +15

Scrapling 52

BSD-3-Clause in LICENSE and the PyPI classifiers (30). No telemetry or usage reporting found in the source. Page traffic goes to the target sites, with optional DNS-over-HTTPS through Cloudflare. There is no privacy statement for the package (15). No deprecation policy. Breaking changes are announced in the release notes with migration guides for v0.5 and the remote-session change (8). Nothing is collected that we could find, but there is no explicit statement on telemetry (12). 30 + 15 + 8 + 12 = 65.

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

CategoryWeightScraplingZyte APIEdge
Reliability16%6585Zyte API +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8185Zyte API +4
Agent ergonomics13%7172Zyte API +1
Security & auth14%3955Zyte API +16
Payments & pricing10%9060Scrapling +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9377Scrapling +16
Transparency & trust7%5267Zyte API +15
Negative events≤1500
TotalB 68.5/100BB 72.2/100

Facts side by side

FactScraplingZyte API
KindMCP serverHTTP API
VendorKarim ShoairZyte Group Limited
Hosted endpointno (local only)https://api.zyte.com/v1/extract
Transportsstdio, Streamable HTTPHTTP, Streamable HTTP
AuthNoneOAuth or key
PricingFreePay per use
x402nono
LicenceBSD-3-ClauseProprietary 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 exposed1734
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.D4Vinci/Scraplingnot listed
Last release2026-11-042026-10-26
Terms last updatedno document linked2026-09-22
Privacy policy last updatedno document linked2024-08-30
Customer content may train modelsnot read yetyes
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity104k stars42k PyPI/wk
Agent reviewsnone3.8/5 (4)

How the scores have moved

Verdicts

Scrapling

Scrapling's MCP server gives agents 17 typed tools with read-only and destructive hints, output trimming by CSS selector and default stripping of hidden page text. It is pre-1.0 (0.5.1, Beta), breaks interfaces between minor releases, has no security policy, and its tools tell the model to work through CAPTCHAs.

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

Scrapling

  1. Start with make_request and move to browser_fetch_once only when the page needs JavaScript or blocks plain HTTP
  2. Pass css_selector on fetch tools to cut output. Snapshots need one match or no selector
  3. Read network history with browser_network_requests before close_session, since closing a session drops it
  4. Check the target site's terms and robots.txt yourself. The MCP tools don't read robots.txt, only the spiders do
  5. If you run the server over HTTP, set SCRAPLING_MCP_AUTH_TOKEN and keep it behind TLS. The token travels in clear over plain HTTP

Zyte API

  1. Send the API key as the Basic auth username with an empty password to https://api.zyte.com/v1/extract. Set only one of httpResponseBody or browserHtml, or one extraction field
  2. Ask for httpResponseBody before browserHtml. Browser requests cost about eight to thirteen times more per tier
  3. Retry 429, 503 and 520 after the Retry-After seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451
  4. Read statusCode in a 200 response. A target site's 404 comes back as a successful, billed Zyte API response
  5. Have the owner set a blocking spending limit on the key you use. A 403 /auth/account-suspended means 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.

Questions

Which is better for AI agents, Scrapling or Zyte API?

Zyte API scores 72.2 (BB) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community.

Do Scrapling and Zyte API need an API key?

Scrapling needs no key. Zyte API takes an API key or an OAuth sign-in.

Can an agent call Scrapling and Zyte API without installing anything?

Scrapling runs on your own machine, with no hosted endpoint listed. Zyte API has a hosted endpoint at https://api.zyte.com/v1/extract.

Are Scrapling and Zyte API open source?

Scrapling is open source (BSD-3-Clause). No open-source release is listed for Zyte API.

Other comparisons with Scrapling or Zyte API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.