{ "data": { "a": { "slug": "crw", "name": "fastCRW", "vendor": "Nanofy OÜ", "vendorUrl": "https://fastcrw.com", "kind": "http-api", "category": "web-scrapers", "summary": "fastCRW is a Firecrawl-compatible scraping engine in Rust from Nanofy OÜ in Estonia. It turns pages into Markdown or JSON and searches, maps and crawls sites, as an AGPL-3.0 self-hosted binary or a hosted API with an MCP server.", "url": "https://www.anchorterminal.com/tools/crw", "markdownUrl": "https://www.anchorterminal.com/tools/crw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crw.json", "dns": "crw.grade.anchorterminal.com", "repo": "https://github.com/fastcrw/crw", "license": "AGPL-3.0", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://fastcrw.com/mcp", "packages": [ { "registry": "npm", "name": "crw-mcp" }, { "registry": "npm", "name": "crw-sdk" }, { "registry": "pypi", "name": "crw" }, { "registry": "cargo", "name": "crw-server" }, { "registry": "oci", "name": "ghcr.io/fastcrw/crw" } ], "auth": "mixed", "authNotes": "Hosted API at api.fastcrw.com takes `Authorization: Bearer crw_live_...` keys from the fastcrw.com dashboard after a browser signup (GitHub or email). The hosted MCP server at fastcrw.com/mcp takes OAuth 2.1 (PKCE S256, dynamic client registration, one scope `mcp:tools`) or the key in the URL path as fastcrw.com/mcp/\u003cAPI_KEY\u003e. No key scopes found. A self-hosted engine needs no key unless `[auth] api_keys` is set.", "pricing": "freemium", "pricingNotes": "500 one-off credits with no card, plus up to 500 more from onboarding tasks. Hobby $13 a month for 5,000 credits, Standard $69 for 100,000, Growth $279 for 500,000, Scale $549 for 1,000,000 (less with yearly billing). One credit a page on any renderer, search 2. Failed pages refunded, top-ups never expire. Self-hosting is free.", "priceSummary": "$13 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the credit-costs and agent-onboarding docs, or the OpenAPI spec (checked 2026-11-06). A 402 on the hosted API means an exhausted credit balance (`errorCode: insufficient_credits`) with an upgrade URL header, not a payment requirement.", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": 1200, "npmWeekly": 881, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.fastcrw.com", "llmsTxt": "https://docs.fastcrw.com/llms.txt", "openapi": "https://github.com/fastcrw/crw/blob/main/docs/openapi.json", "registryName": "io.github.fastcrw/crw", "capabilities": [ "web.scrape", "web.crawl", "web.extract", "scraping.js-render", "scraping.proxies", "web.search", "web.fetch" ], "tags": [ "hosted", "local", "open-source", "self-hosted", "freemium", "no-card", "mcp", "remote-mcp", "mcp-registry", "llms-txt", "openapi", "rust", "eu" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 64.3, "grade": "B", "agentReady": false, "rank": 478, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.", "bestFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "strengths": [ "11 MCP tools, each annotated readOnlyHint, destructiveHint and idempotentHint, with output capped near 15,000 characters and a resume offset", "Public OpenAPI 3.1 spec, llms.txt and an error page that says which codes to retry and which to stop on", "Failed and blocked pages are refunded, every renderer costs 1 credit, and top-up credits never expire", "Released 16 times in the 90 days to 6 November 2026, with five open issues on GitHub", "AGPL-3.0 engine runs self-hosted with no account, and MIT Python and TypeScript SDKs" ], "weaknesses": [ "The status page shows a live check and an uptime objective but no incident history", "The hosted MCP address fastcrw.com/mcp/\u003cAPI_KEY\u003e puts the key in the URL path as a documented option", "Terms and privacy policy name no legal entity, give no retention periods and name no DPA; only the support page names Nanofy OÜ", "No SLA terms beyond an Enterprise mention, no security.txt and no certification found", "No machine payment protocol, and hosted keys need a person to sign up in a browser" ], "agentNotes": [ "Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs", "Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying", "Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`", "Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`", "Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.3 } ], "editorialScores": { "ergonomics": 91, "maintenance": 93, "payments": 35, "reliability": 50, "schema": 91, "security": 40, "transparency": 53 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y crw-mcp@latest install", "http": "curl -X POST https://api.fastcrw.com/v1/scrape -H \"Authorization: Bearer YOUR_API_KEY\" -H \"Content-Type: application/json\" -d '{\"url\":\"https://example.com\",\"formats\":[\"markdown\"]}'" }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/crw" }, "area": "web-data", "unitPrices": [ { "item": "Hobby plan", "unit": "month", "usd": 13, "note": "5,000 credits; $11 a month billed yearly" }, { "item": "Standard plan", "unit": "month", "usd": 69, "note": "100,000 credits; $59 a month billed yearly" }, { "item": "Hobby top-up", "unit": "1k-pages", "usd": 9, "note": "one credit scrapes one page on any renderer" }, { "item": "Scale top-up", "unit": "1k-pages", "usd": 0.6, "note": "$299 for 500,000 credits" } ], "provenance": { "legalEntity": "Nanofy OÜ", "domain": "fastcrw.com", "domainRegistered": "2026-03-05", "endpointOnVendorDomain": true, "terms": "https://fastcrw.com/terms", "privacy": "https://fastcrw.com/privacy", "statusPage": "https://fastcrw.com/status", "changelog": "https://github.com/fastcrw/crw/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "Nanofy OÜ (registry code 17365846, Sepapaja tn 6, Tallinn) is named as operator on fastcrw.com/support. The terms (last updated 4 April 2026) and the privacy policy (undated) name only fastCRW and 'the jurisdiction in which fastCRW operates'.", "The terms forbid crawling sites against their terms or robots.txt and put responsibility for targets on the customer. No clause forbids automated access to fastcrw.com itself.", "fastcrw.com/robots.txt allows all crawlers except account, API and login paths; docs.fastcrw.com/robots.txt allows all.", "RDAP gives fastcrw.com a registration date of 5 March 2026.", "fastcrw.com/.well-known/security.txt answers 404. SECURITY.md in the repository names security@fastcrw.com and GitHub private vulnerability reporting." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crw.json", "live": { "slug": "crw", "probe": { "target": "https://fastcrw.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:19.526009674Z", "lastOk": true, "lastStatus": 401, "lastMs": 156, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 80, "p95ms24h": 153, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://fastcrw.com/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:35.720864858Z" }, "versions": [ { "registry": "github", "name": "fastcrw/crw", "version": "v0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.669809831Z" }, { "registry": "mcp-registry", "name": "io.github.fastcrw/crw", "version": "0.42.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "crw-mcp", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.329470936Z" }, { "registry": "npm", "name": "crw-sdk", "version": "0.42.1", "seenAt": "2026-11-06T23:18:46.739900633Z" }, { "registry": "pypi", "name": "crw", "version": "0.42.1", "released": "2026-11-06", "seenAt": "2026-11-06T23:18:48.550796676Z" } ], "githubStars": 1230, "npmWeekly": 881, "pypiWeekly": 441, "securityTxt": { "url": "https://fastcrw.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:50.596126033Z" }, "llmsTxt": { "url": "https://docs.fastcrw.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:13.945191217Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/fastcrw/crw/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:20:49.992321515Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "572aa4127341" }, { "url": "https://fastcrw.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:09:41.233044196Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "56adab90a2ac" }, { "url": "https://fastcrw.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:09:43.278176432Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4f55b83dc108" } ], "updatedAt": "2026-11-07T18:20:19.526009674Z" } }, "answer": "Zyte API scores 69.7 (B) on agent readiness against fastCRW's 64.3 (B), and leads in 4 of 7 scored categories. fastCRW leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.", "b": { "slug": "zyte", "name": "Zyte API", "vendor": "Zyte Group Limited", "vendorUrl": "https://www.zyte.com", "kind": "http-api", "category": "web-scrapers", "summary": "Zyte API is a hosted web scraping API from Zyte Group Limited of Cork, Ireland. One endpoint returns a page's HTTP body, browser-rendered HTML, a screenshot or extracted structured data, with ban avoidance handled by the service.", "url": "https://www.anchorterminal.com/tools/zyte", "markdownUrl": "https://www.anchorterminal.com/tools/zyte.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zyte.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zyte.json", "dns": "zyte.grade.anchorterminal.com", "repo": "https://github.com/zytedata/python-zyte-api", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.zyte.com/v1/extract", "packages": [ { "registry": "pypi", "name": "zyte-api" }, { "registry": "pypi", "name": "scrapy-zyte-api" } ], "auth": "mixed", "authNotes": "Self-serve API key from the Zyte dashboard, sent as the HTTP Basic username with an empty password. An organisation can hold several keys, and an owner can put a blocking spending limit on each. The Stats API takes a separate dashboard key. Zyte MCP signs in with OAuth (scope `zapi:read` in its metadata) and then calls the API with a dedicated key, `mcp_access_key`. CDP browser sessions need a paid plan or spending limit and business verification.", "pricing": "usage", "pricingNotes": "$5 free credit for the first billing month on signup, with no card per the site, so an agent's owner can start without a contract. After that, pay-as-you-go from $0.13 to $1.27 per 1,000 successful HTTP requests and $1.01 to $16.08 per 1,000 browser requests, by the target site's tier (1 to 5). Screenshots add $1.34 per 1,000 and automatic extraction $0.27 to $1.07 per 1,000. Monthly commitments of $100 to $500 take 25 to 52 per cent off. Failed, banned and rate-limited requests are free (https://www.zyte.com/pricing/, https://docs.zyte.com/zyte-api/pricing.md).", "priceSummary": "$0.13 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "The official Python client documents x402 payment with an Ethereum key against `https://api-x402.zyte.com/v1/` (`python-zyte-api`, `docs/use/x402.rst`, since 0.8.0 of 7 August 2025). One unauthenticated POST to `/v1/extract` on that host on 2026-10-09 returned 401 `/auth/not-valid` with `WWW-Authenticate: Basic` and no 402 challenge. docs.zyte.com and the pricing page don't mention x402 (checked 2026-10-09).", "endpoints": [] }, "toolCount": 34, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 41866, "asOf": "2026-10-09" }, "docsUrl": "https://docs.zyte.com/zyte-api/get-started.html", "llmsTxt": "https://docs.zyte.com/llms.txt", "openapi": "https://docs.zyte.com/zyte-api/usage/reference.md", "capabilities": [ "web.scrape", "scraping.anti-bot", "scraping.js-render", "scraping.proxies", "web.extract", "scraping.screenshot", "browser.hosted", "search.serp" ], "tags": [ "hosted", "usage-based", "free-trial", "no-card", "mcp", "oauth", "openapi", "llms-txt", "proxies", "python", "status-page", "iso-27001", "closed-source" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 69.7, "grade": "B", "agentReady": false, "rank": 228, "ranked": true, "rankOf": 1486, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 77, "payments": 40, "reliability": 85, "schema": 85, "security": 55, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.0.3 contract for `/v1/extract` printed in the reference, with 51 enums and request examples, plus llms.txt and Markdown twins of the docs pages", "Only successful responses are billed. Rate-limited, banned and failed requests are free, per the pricing page and the terms", "429, 503 and 520 responses carry `Retry-After`, and the docs publish a backoff table for each retry", "Blocking spend limits can be set per API key, and the MCP server uses its own key, `mcp_access_key`, signed in over OAuth", "Status page with ten components and incident history, ISO 27001 certification and a list of 36 sub-processors with addresses" ], "weaknesses": [ "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", "No dated changelog or deprecation policy for the API was found in the 150-page docs sitemap, and the terms allow changes with or without notice", "The terms let Zyte use Service Data, data feeds and code from the services for product development and product training", "The official client documents x402 at `api-x402.zyte.com`, but our unauthenticated requests there on 9 October and 1 November 2026 got 401 and no payment challenge", "Zyte MCP lists 34 tools, 26 of them for Scrapy Cloud, and some delete schedules and collections with no undo", "No security.txt, no paid bug bounty, and one official client language (Python)", "The Python client raised its `brotli` floor for CVE-2026-111497, a flaw in brotli, on 26 October, with no release since 0.11.0 of 23 July" ], "agentNotes": [ "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", "Ask for `httpResponseBody` before `browserHtml`. Browser requests cost about eight to thirteen times more per tier", "Retry 429, 503 and 520 after the `Retry-After` seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451", "Read `statusCode` in 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-suspended` means the limit or the trial month ended" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.7 } ], "editorialScores": { "ergonomics": 72, "maintenance": 77, "payments": 40, "reliability": 85, "schema": 85, "security": 55, "transparency": 58 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-27", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install zyte-api", "http": "curl \\\n --user YOUR_ZYTE_API_KEY: \\\n --header 'Content-Type: application/json' \\\n --data '{\"url\": \"https://toscrape.com\", \"httpResponseBody\": true}' \\\n --compressed \\\n https://api.zyte.com/v1/extract", "claudeCode": "claude mcp add --transport http zyte https://mcp.zyte.com/v1/mcp", "config": { "mcpServers": { "zyte": { "type": "http", "url": "https://mcp.zyte.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/zyte" }, "area": "web-data", "unitPrices": [ { "item": "HTTP request, tier 1 site, pay-as-you-go", "unit": "1k-requests", "usd": 0.13, "note": "Tiers 2 to 5 cost $0.23, $0.44, $0.70 and $1.27" }, { "item": "HTTP request, tier 5 site, pay-as-you-go", "unit": "1k-requests", "usd": 1.27, "note": "Only successful responses are billed" }, { "item": "Browser request, tier 1 site, pay-as-you-go", "unit": "1k-requests", "usd": 1.01, "note": "Tiers 2 to 5 cost $2.01, $4.02, $8.04 and $16.08" }, { "item": "Browser request, tier 5 site, pay-as-you-go", "unit": "1k-requests", "usd": 16.08, "note": "Actions and network capture cost extra" }, { "item": "Screenshot, added to a browser request", "unit": "1k-requests", "usd": 1.34, "note": "Pay-as-you-go price" }, { "item": "HTTP request, tier 1 site, $500 commitment", "unit": "1k-requests", "usd": 0.06, "note": "52 per cent volume discount" } ], "provenance": { "legalEntity": "Zyte Group Limited", "domain": "zyte.com", "domainRegistered": "1999-02-22", "endpointOnVendorDomain": true, "terms": "https://www.zyte.com/terms-policies/terms-of-service/", "privacy": "https://www.zyte.com/terms-policies/privacy-policy/", "statusPage": "https://status.zyte.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The terms of service (last updated 22 September 2026) define Zyte as Zyte Group Limited, an Irish company, number 492771, with a notice address at 12 South Mall, Cork. They contain a Zyte API Terms section, so they govern the API.", "The privacy policy is dated 30 August 2024 and covers the websites and the services. It says it does not apply to personal data a customer collects with the services.", "www.zyte.com/.well-known/security.txt returned 404. Reports go through the responsible disclosure programme page, which pays no rewards.", "No dated changelog for the API was found. The Python client and the agent plugin each keep one in their repository.", "RDAP at Verisign gives a registration date of 1999-02-22 for zyte.com.", "The API answers at api.zyte.com and the MCP server at mcp.zyte.com. Its OAuth metadata names auth.app.zyte.com as the authorisation server." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zyte.json", "live": { "slug": "zyte", "probe": { "target": "https://api.zyte.com/v1/extract", "method": "get", "lastAt": "2026-11-07T18:21:08.092593616Z", "lastOk": true, "lastStatus": 405, "lastMs": 411, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 355, "p95ms24h": 487, "samples24h": 239, "samples30d": 7289, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.zyte.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:22:13.569133099Z" }, "versions": [ { "registry": "pypi", "name": "scrapy-zyte-api", "version": "0.37.0", "released": "2026-11-06", "seenAt": "2026-11-07T00:19:43.383179858Z" }, { "registry": "pypi", "name": "zyte-api", "version": "0.11.0", "released": "2026-07-23", "seenAt": "2026-11-07T00:19:43.202687252Z" } ], "githubStars": 30, "pypiWeekly": 73576, "securityTxt": { "url": "https://zyte.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:15.274413557Z" }, "llmsTxt": { "url": "https://docs.zyte.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:33.716227403Z" }, "domain": { "domain": "zyte.com", "registered": "1999-02-22", "source": "https://rdap.verisign.com/com/v1/domain/zyte.com", "checkedAt": "2026-11-01T14:21:07.081929004Z" }, "pages": [ { "url": "https://docs.zyte.com/zyte-api/pricing.md", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:08:54.49631742Z", "changedAt": "2026-10-24T02:17:08.882124443Z", "fingerprint": "c8c695a7b7fe" }, { "url": "https://www.zyte.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:38:04.990833373Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d8f74b8aaa20" }, { "url": "https://www.zyte.com/terms-policies/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:38:09.200579932Z", "changedAt": "2026-11-05T13:20:43.434631379Z", "fingerprint": "44769870b633" }, { "url": "https://www.zyte.com/terms-policies/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:38:09.688475603Z", "changedAt": "2026-11-05T13:20:45.78474037Z", "fingerprint": "6bc3bdc4893e" } ], "mcpTools": { "url": "https://mcp.zyte.com/v1/mcp", "checkedAt": "2026-11-07T01:49:32.045008424Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:49:32.045008424Z" }, "github": { "repo": "zytedata/python-zyte-api", "checkedAt": "2026-11-02T09:41:11.19839569Z", "stars": 30, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-27T08:25:43Z", "openIssues": 1, "openPRs": 2, "issuesOpened90d": 1, "issuesClosed90d": 8, "prsMerged90d": 14, "ci": { "branch": "main", "runs": 28, "success": 21, "failure": 7, "other": 0, "latest": "success", "latestAt": "2026-10-27T08:27:40Z" }, "replies": { "sampled": 25, "unanswered": 1, "medianDays": 8.6 } }, "updatedAt": "2026-11-07T18:22:13.569133099Z" } }, "edges": [ { "by": 35, "category": "reliability", "leads": "zyte", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50.", "b": "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)." }, "scores": { "a": 50, "b": 85 } }, { "by": 19, "category": "ergonomics", "leads": "crw", "name": "Agent ergonomics", "reasons": { "a": "11 compact MCP tools, two of them the data-source tools added in 0.41.0. Content is capped near 15,000 characters with `truncated: true` and a resume offset, and map returns at most 100 URLs by default (20 of 25). Formats, main-content filtering, include and exclude selectors, maxLength, startIndex, limit and crawl depth and page caps (20). Errors carry `errorCode` values such as anti_bot, insufficient_credits and llm_not_available with a retry table, though an anti-bot wall answers HTTP 200 with `success: false` (19 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, cancel is idempotent and failed pages are refunded, but job starts take no idempotency key (17 of 20). Only `url` is required, with official Python and TypeScript SDKs (15). 20 + 20 + 19 + 17 + 15 = 91.", "b": "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)." }, "scores": { "a": 91, "b": 72 } }, { "by": 16, "category": "maintenance", "leads": "crw", "name": "Maintenance \u0026 community", "reasons": { "a": "v0.41.0 on 4 November 2026, matching the registry and npm (30). 16 dated releases in the 90 days from 8 August, from 0.37.0 to 0.41.0 (20). Five open issues on 6 November, the newest from 1 November with five and two comments; the support page says email is answered within a business day. Reply authors weren't read (18 of 25). In the official MCP registry as io.github.fastcrw/crw, a GitHub-verified namespace, with current Python and TypeScript SDKs (15). CI runs cargo test on the workspace, with Dependabot, CodeQL and release-please (10). 30 + 20 + 18 + 15 + 10 = 93.", "b": "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)." }, "scores": { "a": 93, "b": 77 } }, { "by": 15, "category": "security", "leads": "zyte", "name": "Security \u0026 auth", "reasons": { "a": "The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40.", "b": "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)." }, "scores": { "a": 40, "b": 55 } }, { "by": 7, "category": "transparency", "leads": "zyte", "name": "Transparency \u0026 trust", "reasons": { "a": "The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53.", "b": "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)." }, "scores": { "a": 60, "b": 67 } }, { "by": 6, "category": "schema", "leads": "crw", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 for 11 paths at version 0.41.0 in docs/openapi.json, checked against the server in CI, and typed JSON Schema inputs on every MCP tool (25). llms.txt (86 lines), llms-full.txt and Markdown sources for every docs page (10). Tool descriptions state purpose and how to chain them (crawl returns a job id to poll, map returns URLs only, extract needs an LLM), and the docs have a choose-an-endpoint page, but few descriptions say when not to use a tool (14 of 20). Inputs are typed with required fields and a renderer enum, though crawl and extract take a free-form JSON Schema object (12 of 15). Examples on every page and an errors page with each HTTP status, errorCode and next step (15). Semver releases with a dated CHANGELOG that flags breaking changes (15). 25 + 10 + 14 + 12 + 15 + 15 = 91.", "b": "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)." }, "scores": { "a": 91, "b": 85 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nanofy OÜ", "b": "Zyte Group Limited", "name": "Vendor" }, { "a": "https://fastcrw.com/mcp", "b": "https://api.zyte.com/v1/extract", "name": "Hosted endpoint" }, { "a": "stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "AGPL-3.0", "b": "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", "name": "Licence" }, { "a": "11", "b": "34", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.fastcrw/crw", "b": "not listed", "name": "MCP registry" }, { "a": "2026-11-04", "b": "2026-10-26", "name": "Last release" }, { "a": "2026-04-04", "b": "2026-09-22", "name": "Terms last updated" }, { "a": "no date given", "b": "2024-08-30", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1.2k stars, 881 npm/wk", "b": "42k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Zyte API scores 69.7 (B) on agent readiness against fastCRW's 64.3 (B), and leads in 4 of 7 scored categories. fastCRW leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, fastCRW or Zyte API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do fastCRW and Zyte API need an API key?" }, { "answer": "Yes. fastCRW has a hosted endpoint at https://fastcrw.com/mcp and Zyte API at https://api.zyte.com/v1/extract.", "question": "Can an agent call fastCRW and Zyte API without installing anything?" }, { "answer": "fastCRW is open source (AGPL-3.0). No open-source release is listed for Zyte API.", "question": "Are fastCRW and Zyte API open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 91 against 85", "Agent ergonomics, 91 against 72", "Maintenance \u0026 community, 93 against 77" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.", "slug": "crw", "watchFor": "The status page shows a live check and an uptime objective but no incident history" }, { "aheadOn": [ "Reliability, 85 against 50", "Security \u0026 auth, 55 against 40", "Payments \u0026 pricing, 40 against 35", "Transparency \u0026 trust, 67 against 60" ], "also": null, "goodFor": "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.", "slug": "zyte", "watchFor": "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" } ], "history": { "crw": null, "zyte": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 69.7, "fromGrade": "B", "to": 69.7, "toGrade": "B" } ] }, "job": { "capability": "web.scrape", "name": "Scraping" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.json", "title": "Apify MCP Server vs Zyte API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-crw.json", "title": "Bright Data vs fastCRW", "url": "https://www.anchorterminal.com/compare/bright-data-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/bright-data-vs-zyte.json", "title": "Bright Data vs Zyte API", "url": "https://www.anchorterminal.com/compare/bright-data-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-crw.json", "title": "BrowserAct vs fastCRW", "url": "https://www.anchorterminal.com/compare/browseract-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-zyte.json", "title": "BrowserAct vs Zyte API", "url": "https://www.anchorterminal.com/compare/browseract-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-crw.json", "title": "Context.dev vs fastCRW", "url": "https://www.anchorterminal.com/compare/context-dev-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-zyte.json", "title": "Context.dev vs Zyte API", "url": "https://www.anchorterminal.com/compare/context-dev-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw.json", "title": "Crawl4AI vs fastCRW", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-zyte.json", "title": "Crawl4AI vs Zyte API", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-decodo.json", "title": "fastCRW vs Decodo Web Data API", "url": "https://www.anchorterminal.com/compare/crw-vs-decodo" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-diffbot.json", "title": "fastCRW vs Diffbot", "url": "https://www.anchorterminal.com/compare/crw-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl.json", "title": "fastCRW vs jevcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-jevcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-jina-reader.json", "title": "fastCRW vs Jina Reader", "url": "https://www.anchorterminal.com/compare/crw-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-microlink.json", "title": "fastCRW vs Microlink", "url": "https://www.anchorterminal.com/compare/crw-vs-microlink" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-olostep.json", "title": "fastCRW vs Olostep", "url": "https://www.anchorterminal.com/compare/crw-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-outcrawl.json", "title": "fastCRW vs Outcrawl", "url": "https://www.anchorterminal.com/compare/crw-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.json", "title": "fastCRW vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrape-do.json", "title": "fastCRW vs Scrape.do", "url": "https://www.anchorterminal.com/compare/crw-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.json", "title": "fastCRW vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeless.json", "title": "fastCRW vs Scrapeless", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeops.json", "title": "fastCRW vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scraperapi.json", "title": "fastCRW vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/crw-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapewise.json", "title": "fastCRW vs Scrapewise", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapfly.json", "title": "fastCRW vs Scrapfly", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingant.json", "title": "fastCRW vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee.json", "title": "fastCRW vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog.json", "title": "fastCRW vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud.json", "title": "fastCRW vs Spider", "url": "https://www.anchorterminal.com/compare/crw-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.json", "title": "fastCRW vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/crw-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-zenrows.json", "title": "fastCRW vs ZenRows", "url": "https://www.anchorterminal.com/compare/crw-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-zyte.json", "title": "Decodo Web Data API vs Zyte API", "url": "https://www.anchorterminal.com/compare/decodo-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-zyte.json", "title": "jevcrawl vs Zyte API", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-zyte.json", "title": "Jina Reader vs Zyte API", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/microlink-vs-zyte.json", "title": "Microlink vs Zyte API", "url": "https://www.anchorterminal.com/compare/microlink-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-zyte.json", "title": "Olostep vs Zyte API", "url": "https://www.anchorterminal.com/compare/olostep-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/outcrawl-vs-zyte.json", "title": "Outcrawl vs Zyte API", "url": "https://www.anchorterminal.com/compare/outcrawl-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte.json", "title": "Oxylabs Web Scraper API vs Zyte API", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-zyte.json", "title": "Scrape.do vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte.json", "title": "ScrapeGraphAI vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-zyte.json", "title": "Scrapeless vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-zyte.json", "title": "ScraperAPI vs Zyte API", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte.json", "title": "Scrapewise vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapfly-vs-zyte.json", "title": "Scrapfly vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapfly-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapingant-vs-zyte.json", "title": "ScrapingAnt vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingant-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapingbee-vs-zyte.json", "title": "ScrapingBee vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingbee-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapingdog-vs-zyte.json", "title": "Scrapingdog vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapingdog-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.json", "title": "Spider vs Zyte API", "url": "https://www.anchorterminal.com/compare/spider-cloud-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/webscraping-ai-vs-zyte.json", "title": "WebScraping.AI vs Zyte API", "url": "https://www.anchorterminal.com/compare/webscraping-ai-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/zenrows-vs-zyte.json", "title": "ZenRows vs Zyte API", "url": "https://www.anchorterminal.com/compare/zenrows-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp.json", "title": "fastCRW vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-qovia.json", "title": "fastCRW vs Qovia", "url": "https://www.anchorterminal.com/compare/crw-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.json", "title": "fastCRW vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-soldfetch.json", "title": "fastCRW vs SoldFetch", "url": "https://www.anchorterminal.com/compare/crw-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-zyte.json", "title": "Diffbot vs Zyte API", "url": "https://www.anchorterminal.com/compare/diffbot-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-zyte.json", "title": "Qovia vs Zyte API", "url": "https://www.anchorterminal.com/compare/qovia-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte.json", "title": "ScrapeAtlas vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/soldfetch-vs-zyte.json", "title": "SoldFetch vs Zyte API", "url": "https://www.anchorterminal.com/compare/soldfetch-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw.json", "title": "Apify MCP Server vs fastCRW", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-crw" }, { "json": "https://www.anchorterminal.com/compare/scrapeops-vs-zyte.json", "title": "ScrapeOps Proxy API Aggregator vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapeops-vs-zyte" } ], "panel": null, "scores": [ { "by": 35, "crw": 50, "edge": "zyte", "key": "reliability", "name": "Reliability", "weight": 16, "zyte": 85 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "crw": 91, "edge": "crw", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zyte": 85 }, { "by": 19, "crw": 91, "edge": "crw", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zyte": 72 }, { "by": 15, "crw": 40, "edge": "zyte", "key": "security", "name": "Security \u0026 auth", "weight": 14, "zyte": 55 }, { "by": 5, "crw": 35, "edge": "zyte", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zyte": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "crw": 93, "edge": "crw", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zyte": 77 }, { "by": 7, "crw": 60, "edge": "zyte", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zyte": 67 } ], "summary": "Zyte API scores 69.7 (B) on agent readiness against fastCRW's 64.3 (B), and leads in 4 of 7 scored categories. fastCRW leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community. Both do scraping.", "tasks": null, "tutorials": [ { "title": "Retrieve and decode HTML with Zyte", "tool": "zyte", "url": "https://www.anchorterminal.com/tutorials/zyte/" } ], "verdicts": { "crw": "Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.", "zyte": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/crw-vs-zyte", "json": "https://www.anchorterminal.com/compare/crw-vs-zyte.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crw-vs-zyte.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/crw-vs-zyte.min.md" }, "markdown": "Zyte API scores 69.7 (B) on agent readiness against fastCRW's 64.3 (B), and leads in 4 of 7 scored categories. fastCRW leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community. Both do scraping.\n\n- fastCRW: grade B, 64.3/100, rank #478 of 1486. Markdown https://www.anchorterminal.com/tools/crw.md · JSON https://www.anchorterminal.com/api/v1/tools/crw.json\n- Zyte API: grade B, 69.7/100, rank #228 of 1486. Markdown https://www.anchorterminal.com/tools/zyte.md · JSON https://www.anchorterminal.com/api/v1/tools/zyte.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 501 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### fastCRW (B)\n\nGood for: Agents that want Firecrawl-style scrape, crawl, map, search and extract at lower per-page cost, or a small self-hosted engine.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 85\n- Agent ergonomics, 91 against 72\n- Maintenance \u0026 community, 93 against 77\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: The status page shows a live check and an uptime objective but no incident history\n\n### Zyte API (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 85 against 50\n- Security \u0026 auth, 55 against 40\n- Payments \u0026 pricing, 40 against 35\n- Transparency \u0026 trust, 67 against 60\n\nWatch 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\n\n\n## Why the edge\n\n### Reliability: Zyte API +35\n\n- fastCRW (50): Graded on the hosted lines, for the hosted API and MCP server an agent would call; the self-hosted engine would read higher on the local lines. fastcrw.com/status is a first-party page with a live health check and a 99.9% monthly uptime objective, but no components with history (10 of 20). It lists no incidents and keeps no history we could read (5). Concurrency per plan is published, 3 on Free to 150 on Scale, while the request-rate guard above it is deliberately unpublished (12 of 15). The rate-limits page documents Retry-After and X-RateLimit headers, gives exponential backoff code, and separates 429 (retry) from 402 (stop). No idempotency keys for crawl, extract or monitor starts (13 of 15). Pricing mentions an SLA only as 'Premier + SLA' on Enterprise, with no terms, and the terms promise no uptime (0). The hosted service is sold on paid plans with no beta label, though the engine is at 0.41.0 (10). 10 + 5 + 12 + 13 + 0 + 10 = 50.\n- 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).\n\n### Agent ergonomics: fastCRW +19\n\n- fastCRW (91): 11 compact MCP tools, two of them the data-source tools added in 0.41.0. Content is capped near 15,000 characters with `truncated: true` and a resume offset, and map returns at most 100 URLs by default (20 of 25). Formats, main-content filtering, include and exclude selectors, maxLength, startIndex, limit and crawl depth and page caps (20). Errors carry `errorCode` values such as anti_bot, insufficient_credits and llm_not_available with a retry table, though an anti-bot wall answers HTTP 200 with `success: false` (19 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, cancel is idempotent and failed pages are refunded, but job starts take no idempotency key (17 of 20). Only `url` is required, with official Python and TypeScript SDKs (15). 20 + 20 + 19 + 17 + 15 = 91.\n- 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).\n\n### Maintenance \u0026 community: fastCRW +16\n\n- fastCRW (93): v0.41.0 on 4 November 2026, matching the registry and npm (30). 16 dated releases in the 90 days from 8 August, from 0.37.0 to 0.41.0 (20). Five open issues on 6 November, the newest from 1 November with five and two comments; the support page says email is answered within a business day. Reply authors weren't read (18 of 25). In the official MCP registry as io.github.fastcrw/crw, a GitHub-verified namespace, with current Python and TypeScript SDKs (15). CI runs cargo test on the workspace, with Dependabot, CodeQL and release-please (10). 30 + 20 + 18 + 15 + 10 = 93.\n- 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).\n\n### Security \u0026 auth: Zyte API +15\n\n- fastCRW (40): The hosted MCP server publishes RFC 9728 metadata naming its own authorisation server, with PKCE S256, dynamic client registration and one scope, `mcp:tools`, and the API takes revocable Bearer keys from the dashboard. No key scopes or second scope found (22). The authentication page documents fastcrw.com/mcp/\u003cAPI_KEY\u003e as a way in, a key in the URL path, so less 10 (12 of 30). Tools mostly read, and data-source calls check approvals, but there is no read-only key or confirmation step for monitors (8 of 20). Managed LLM extraction, summaries and answers wrap scraped text in a nonce fence (crates/crw-extract/src/untrusted.rs), and the hardening guide treats pages as untrusted, but the MCP docs give agents no guidance on scraped content (7 of 15). Each response reports `creditsUsed`; no per-call log in the docs (5 of 15). SECURITY.md names security@fastcrw.com and GitHub private reporting with a 48-hour acknowledgement, and CI runs CodeQL and OpenSSF Scorecard. security.txt answers 404, and no bounty or certification found (8 of 20). 12 + 8 + 7 + 5 + 8 = 40.\n- 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).\n\n### Transparency \u0026 trust: Zyte API +7\n\n- fastCRW (60): The engine and MCP server are AGPL-3.0 and the SDKs MIT, while the hosted control plane is closed under terms that name no legal entity (25 of 30). The terms say crawled data is handled transiently with zero data retention for approved accounts, but the privacy policy is undated, names no controller, gives no retention periods and mentions no DPA (10 of 30). The CHANGELOG flags breaking changes, deprecated v2 extract routes return a warning on every response, and the October 2026 402 change is dated in the docs, with no standing notice policy (10 of 20). Local data-source telemetry is disclosed with an opt-out. The privacy policy names Stripe, Google Analytics, Google Ads and an X pixel, but infrastructure and search providers are unnamed and no data location is given (8 of 20). 25 + 10 + 10 + 8 = 53.\n- 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).\n\n### Schema \u0026 documentation: fastCRW +6\n\n- fastCRW (91): OpenAPI 3.1 for 11 paths at version 0.41.0 in docs/openapi.json, checked against the server in CI, and typed JSON Schema inputs on every MCP tool (25). llms.txt (86 lines), llms-full.txt and Markdown sources for every docs page (10). Tool descriptions state purpose and how to chain them (crawl returns a job id to poll, map returns URLs only, extract needs an LLM), and the docs have a choose-an-endpoint page, but few descriptions say when not to use a tool (14 of 20). Inputs are typed with required fields and a renderer enum, though crawl and extract take a free-form JSON Schema object (12 of 15). Examples on every page and an errors page with each HTTP status, errorCode and next step (15). Semver releases with a dated CHANGELOG that flags breaking changes (15). 25 + 10 + 14 + 12 + 15 + 15 = 91.\n- 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).\n\n## Score by category\n\n| Category | Weight | fastCRW | Zyte API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 85 | Zyte API +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 91 | 85 | fastCRW +6 |\n| Agent ergonomics | 13% (16.2 this run) | 91 | 72 | fastCRW +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 55 | Zyte API +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Zyte API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 93 | 77 | fastCRW +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 67 | Zyte API +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.3 · B** | **69.7 · B** | |\n\n## Facts side by side\n\n| Fact | fastCRW | Zyte API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nanofy OÜ | Zyte Group Limited |\n| Hosted endpoint | `https://fastcrw.com/mcp` | `https://api.zyte.com/v1/extract` |\n| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | AGPL-3.0 | 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 |\n| Tools exposed | 11 | 34 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.fastcrw/crw` | not listed |\n| Last release | 2026-11-04 | 2026-10-26 |\n| Terms last updated | 2026-04-04 | 2026-09-22 |\n| Privacy policy last updated | no date given | 2024-08-30 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 1.2k stars, 881 npm/wk | 42k PyPI/wk |\n| Agent reviews | none | 3.8/5 (4) |\n\n## How the scores have moved\n\n### fastCRW\n\nNo score change since it was listed.\n\n### Zyte API\n\n- no change on 27 October 2026: checklist\n\n## Verdicts\n\n**fastCRW.** Agents get 11 compact, annotated MCP tools with bounded output, a public OpenAPI spec, refunds on failed pages and a free self-hosted engine. The hosted service has no status history, publishes no SLA terms, names its operator only on the support page, and documents an MCP address with the API key in the URL path.\n\n**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.\n\n## Before you call either\n\n### fastCRW\n\n1. Connect to https://fastcrw.com/mcp with OAuth rather than the /mcp/\u003cAPI_KEY\u003e address, so the key stays out of URLs and logs\n2. Branch on `errorCode`. Stop on 402 insufficient_credits or llm_not_available, and on 429 wait for Retry-After before retrying\n3. Check `success` as well as the HTTP status, since an anti-bot wall answers 200 with `success: false` and `errorCode: anti_bot`\n4. Pass `startIndex` from a truncated result to read the rest of a long page instead of setting `maxLength: 0`\n5. Use native /v1 routes for new work; /firecrawl/v2 is for Firecrawl SDK migrations and keeps the older 429 for empty balances\n\n### Zyte API\n\n1. 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\n2. Ask for `httpResponseBody` before `browserHtml`. Browser requests cost about eight to thirteen times more per tier\n3. Retry 429, 503 and 520 after the `Retry-After` seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451\n4. Read `statusCode` in a 200 response. A target site's 404 comes back as a successful, billed Zyte API response\n5. 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\n\n## Tutorials\n\n- [Retrieve and decode HTML with Zyte](https://www.anchorterminal.com/tutorials/zyte/), for Zyte API\n\n## Questions\n\n### Which is better for AI agents, fastCRW or Zyte API?\n\nZyte API scores 69.7 (B) on agent readiness against fastCRW's 64.3 (B), and leads in 4 of 7 scored categories. fastCRW leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.\n\n### Do fastCRW and Zyte API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call fastCRW and Zyte API without installing anything?\n\nYes. fastCRW has a hosted endpoint at https://fastcrw.com/mcp and Zyte API at https://api.zyte.com/v1/extract.\n\n### Are fastCRW and Zyte API open source?\n\nfastCRW is open source (AGPL-3.0). No open-source release is listed for Zyte API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crw-vs-zyte.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crw-vs-zyte.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crw\", \"b\": \"zyte\"}`. From a terminal: `anchor compare crw zyte`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crw.json and https://www.anchorterminal.com/api/v1/tools/zyte.json\n\n## Other comparisons with fastCRW or Zyte API\n\n- [Apify MCP Server vs Zyte API](https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.md)\n- [Bright Data vs fastCRW](https://www.anchorterminal.com/compare/bright-data-vs-crw.md)\n- [Bright Data vs Zyte API](https://www.anchorterminal.com/compare/bright-data-vs-zyte.md)\n- [BrowserAct vs fastCRW](https://www.anchorterminal.com/compare/browseract-vs-crw.md)\n- [BrowserAct vs Zyte API](https://www.anchorterminal.com/compare/browseract-vs-zyte.md)\n- [Context.dev vs fastCRW](https://www.anchorterminal.com/compare/context-dev-vs-crw.md)\n- [Context.dev vs Zyte API](https://www.anchorterminal.com/compare/context-dev-vs-zyte.md)\n- [Crawl4AI vs fastCRW](https://www.anchorterminal.com/compare/crawl4ai-vs-crw.md)\n- [Crawl4AI vs Zyte API](https://www.anchorterminal.com/compare/crawl4ai-vs-zyte.md)\n- [fastCRW vs Decodo Web Data API](https://www.anchorterminal.com/compare/crw-vs-decodo.md)\n- [fastCRW vs Diffbot](https://www.anchorterminal.com/compare/crw-vs-diffbot.md)\n- [fastCRW vs jevcrawl](https://www.anchorterminal.com/compare/crw-vs-jevcrawl.md)\n- [fastCRW vs Jina Reader](https://www.anchorterminal.com/compare/crw-vs-jina-reader.md)\n- [fastCRW vs Microlink](https://www.anchorterminal.com/compare/crw-vs-microlink.md)\n- [fastCRW vs Olostep](https://www.anchorterminal.com/compare/crw-vs-olostep.md)\n- [fastCRW vs Outcrawl](https://www.anchorterminal.com/compare/crw-vs-outcrawl.md)\n- [fastCRW vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/crw-vs-oxylabs-web-scraper.md)\n- [fastCRW vs Scrape.do](https://www.anchorterminal.com/compare/crw-vs-scrape-do.md)\n- [fastCRW vs ScrapeGraphAI](https://www.anchorterminal.com/compare/crw-vs-scrapegraphai.md)\n- [fastCRW vs Scrapeless](https://www.anchorterminal.com/compare/crw-vs-scrapeless.md)\n- [fastCRW vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/crw-vs-scrapeops.md)\n- [fastCRW vs ScraperAPI](https://www.anchorterminal.com/compare/crw-vs-scraperapi.md)\n- [fastCRW vs Scrapewise](https://www.anchorterminal.com/compare/crw-vs-scrapewise.md)\n- [fastCRW vs Scrapfly](https://www.anchorterminal.com/compare/crw-vs-scrapfly.md)\n- [fastCRW vs ScrapingAnt](https://www.anchorterminal.com/compare/crw-vs-scrapingant.md)\n- [fastCRW vs ScrapingBee](https://www.anchorterminal.com/compare/crw-vs-scrapingbee.md)\n- [fastCRW vs Scrapingdog](https://www.anchorterminal.com/compare/crw-vs-scrapingdog.md)\n- [fastCRW vs Spider](https://www.anchorterminal.com/compare/crw-vs-spider-cloud.md)\n- [fastCRW vs WebScraping.AI](https://www.anchorterminal.com/compare/crw-vs-webscraping-ai.md)\n- [fastCRW vs ZenRows](https://www.anchorterminal.com/compare/crw-vs-zenrows.md)\n- [Decodo Web Data API vs Zyte API](https://www.anchorterminal.com/compare/decodo-vs-zyte.md)\n- [jevcrawl vs Zyte API](https://www.anchorterminal.com/compare/jevcrawl-vs-zyte.md)\n- [Jina Reader vs Zyte API](https://www.anchorterminal.com/compare/jina-reader-vs-zyte.md)\n- [Microlink vs Zyte API](https://www.anchorterminal.com/compare/microlink-vs-zyte.md)\n- [Olostep vs Zyte API](https://www.anchorterminal.com/compare/olostep-vs-zyte.md)\n- [Outcrawl vs Zyte API](https://www.anchorterminal.com/compare/outcrawl-vs-zyte.md)\n- [Oxylabs Web Scraper API vs Zyte API](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-zyte.md)\n- [Scrape.do vs Zyte API](https://www.anchorterminal.com/compare/scrape-do-vs-zyte.md)\n- [ScrapeGraphAI vs Zyte API](https://www.anchorterminal.com/compare/scrapegraphai-vs-zyte.md)\n- [Scrapeless vs Zyte API](https://www.anchorterminal.com/compare/scrapeless-vs-zyte.md)\n- [ScraperAPI vs Zyte API](https://www.anchorterminal.com/compare/scraperapi-vs-zyte.md)\n- [Scrapewise vs Zyte API](https://www.anchorterminal.com/compare/scrapewise-vs-zyte.md)\n- [Scrapfly vs Zyte API](https://www.anchorterminal.com/compare/scrapfly-vs-zyte.md)\n- [ScrapingAnt vs Zyte API](https://www.anchorterminal.com/compare/scrapingant-vs-zyte.md)\n- [ScrapingBee vs Zyte API](https://www.anchorterminal.com/compare/scrapingbee-vs-zyte.md)\n- [Scrapingdog vs Zyte API](https://www.anchorterminal.com/compare/scrapingdog-vs-zyte.md)\n- [Spider vs Zyte API](https://www.anchorterminal.com/compare/spider-cloud-vs-zyte.md)\n- [WebScraping.AI vs Zyte API](https://www.anchorterminal.com/compare/webscraping-ai-vs-zyte.md)\n- [ZenRows vs Zyte API](https://www.anchorterminal.com/compare/zenrows-vs-zyte.md)\n- [fastCRW vs Firecrawl MCP](https://www.anchorterminal.com/compare/crw-vs-firecrawl-mcp.md)\n- [fastCRW vs Qovia](https://www.anchorterminal.com/compare/crw-vs-qovia.md)\n- [fastCRW vs ScrapeAtlas](https://www.anchorterminal.com/compare/crw-vs-scrapeatlas.md)\n- [fastCRW vs SoldFetch](https://www.anchorterminal.com/compare/crw-vs-soldfetch.md)\n- [Diffbot vs Zyte API](https://www.anchorterminal.com/compare/diffbot-vs-zyte.md)\n- [Qovia vs Zyte API](https://www.anchorterminal.com/compare/qovia-vs-zyte.md)\n- [ScrapeAtlas vs Zyte API](https://www.anchorterminal.com/compare/scrapeatlas-vs-zyte.md)\n- [SoldFetch vs Zyte API](https://www.anchorterminal.com/compare/soldfetch-vs-zyte.md)\n- [Apify MCP Server vs fastCRW](https://www.anchorterminal.com/compare/apify-mcp-vs-crw.md)\n- [ScrapeOps Proxy API Aggregator vs Zyte API](https://www.anchorterminal.com/compare/scrapeops-vs-zyte.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "fastCRW vs Zyte API", "url": "" } ], "description": "Zyte scores 69.7 (B) to fastCRW's 64.3 (B) for scraping. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "fastCRW B 64.3", "Zyte API B 69.7", "scores" ], "h1": "fastCRW vs Zyte API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/crw-vs-zyte", "published": "2026-10-01", "section": "tools", "title": "fastCRW vs Zyte for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/crw-vs-zyte" }, "tokens": { "markdown": 6050, "slim": 3480 }, "version": 1 }