# BrowserAct vs Zyte API (slim)

> Zyte scores 69.7 (B) to BrowserAct's 44.4 (E) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/browseract-vs-zyte.md (~5,350 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/browseract-vs-zyte.json · canonical https://www.anchorterminal.com/compare/browseract-vs-zyte
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Zyte API scores 69.7 (B) on agent readiness against BrowserAct's 44.4 (E), and leads in every scored category. Both do scraping.

- BrowserAct: E 44.4, rank #1204 of 1486 · https://www.anchorterminal.com/tools/browseract.min.md
- Zyte API: B 69.7, rank #228 of 1486 · https://www.anchorterminal.com/tools/zyte.min.md
- BrowserAct, good for Teams that want no-code, prompt-built scrapers an agent can rerun on a schedule.
- Zyte API, good 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 23; Schema & documentation, 85 against 76; Agent ergonomics, 72 against 49; Security & auth, 55 against 41; Payments & pricing, 40 against 25; Maintenance & community, 77 against 61; Transparency & trust, 67 against 44. Also Free to start without a card.

| Category | BrowserAct | Zyte API |
| --- | --- | --- |
| Reliability (16%) | 23 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 85 |
| Agent ergonomics (13%) | 49 | 72 |
| Security & auth (14%) | 41 | 55 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 77 |
| Transparency & trust (7%) | 44 | 67 |

| Fact (where they differ) | BrowserAct | Zyte API |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | Zyte Group Limited |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://api.zyte.com/v1/extract` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Pay per use |
| 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 | none | 34 |
| Last release | 2026-11-05 | 2026-10-26 |
| Terms last updated | 2025-05-15 | 2026-09-22 |
| Privacy policy last updated | 2025-05-15 | 2024-08-30 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 42k PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Reliability, Zyte API +62: BrowserAct 23 (Hosted reading. No status page found (0) and no readable incident history (5). The docs say there are no rate limits, and give concurrency by plan (2 free, up to 20 for paid API users) and a 7-hour task cap (8). No 429 or retry guidance, and no idempotency keys on task creation (0). No SLA (0). No beta label on the API or MCP server (10). 0 + 5 + 8 + 0 + 0 + 10 = 23.); 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).)
- Agent ergonomics, Zyte API +23: BrowserAct 49 (Graded on the API, since the MCP tool list isn't published. Task results come back whole, with no field selection found (10). Lists of bots, templates and tasks are paginated (15). Errors carry numeric codes with documented meanings for a few cases (12). No idempotency key on task creation; webhooks and a status endpoint avoid polling loops (5). No official SDK in two languages; the CLI is Python (7). 10 + 15 + 12 + 5 + 7 = 49.); Zyte API 72 (Graded on the REST API, with the MCP server noted. A request names the outputs it wants, so an agent can ask for extracted fields or `pageContent` in place of full HTML, but HTML and bodies come whole, up to 10 MB. Zyte MCP lists 34 tools at once, 26 of them for Scrapy Cloud, recounted from its docs on 1 November (15 of 25). No pagination applies to a single-URL call. Search takes `maxResults` from 10 to 100, and the Stats API pages and filters (14 of 20). Errors are problem+json with a stable `type` path, and the docs say which to retry and which to fix (20). Calls are reads, failed and rate-limited requests are free, and retries are safe. We could not read the MCP tool annotations, which need a sign-in (14 of 20). A call needs only `url` and one output flag. The only official client is Python, with a Scrapy plugin (9 of 15).)
- Transparency & trust, Zyte API +23: BrowserAct 44 (Closed service with published terms naming the operating company and governing law (15). The privacy policy of 15 May 2025 states retention by category and that crawled data is kept per plan and deletable by the user (15). No deprecation policy or notices found (0). No sub-processors or data locations named (3). 15 + 15 + 0 + 3 = 33.); 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).)
- Maintenance & community, Zyte API +16: BrowserAct 61 (browser-act-cli 1.6.2 on 5 November 2026, read from PyPI's release feed (30). Six CLI releases from 15 October to 5 November (20). A closed service with a support address, but no public changelog or issue tracker found (8). No official SDKs and no entry in the official MCP registry (0). The CLI package carries no licence or repository in its metadata (3). 30 + 20 + 8 + 0 + 3 = 61.); 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).)
- Payments & pricing, Zyte API +15: BrowserAct 25 (No x402, MPP or L402 (0). Plan prices and credit costs per bot build, run and workflow step are public, but there is no direct per-call price (15). A free plan with 200 credits; whether it needs a card isn't stated (10). A person signs up and creates the key in the dashboard (0). 0 + 15 + 10 + 0 = 25.); Zyte API 40 (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).)
- Security & auth, Zyte API +14: BrowserAct 41 (One account-wide API key type, revocable and listed with last-used time, but without scopes or expiry (18). Confirmation Required mode holds purchases and asset creation or deletion for approval in the BrowserAct page (14). Scraped pages are untrusted, and no prompt-injection guidance was found (3). Keys show last use and runs keep logs (6). No security page, disclosure policy, certification or bug bounty found (0). 18 + 14 + 3 + 6 + 0 = 41.); 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).)