{ "data": { "a": { "slug": "apify-mcp", "name": "Apify MCP Server", "vendor": "Apify", "vendorUrl": "https://apify.com", "kind": "mcp", "category": "web-scrapers", "summary": "Exposes thousands of Apify Store Actors (scrapers, crawlers, automations) as dynamically discovered MCP tools, hosted at mcp.apify.com or run locally; supports OAuth, API tokens and agentic payments (x402 prepaid tokens, Skyfire).", "url": "https://www.anchorterminal.com/tools/apify-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/apify-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/apify-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/apify-mcp.json", "repo": "https://github.com/apify/apify-mcp-server", "license": "MIT", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://mcp.apify.com", "packages": [ { "registry": "npm", "name": "@apify/actors-mcp-server" } ], "auth": "mixed", "authNotes": "OAuth on mcp.apify.com, or an Apify API token as `Authorization: Bearer`. Tokens can be scoped to account or per-resource permissions, given an expiry date and rotated with a 24-hour overlap. The Apify API also accepts the token as a `token` query parameter. Without a token, an agent can pay with AGI prepaid tokens (bought over x402 or MPP), direct x402 (`?payment=x402`, Pay Per Event Actors only) or Skyfire PAY tokens. `?tools=` selects categories or single tools.", "pricing": "freemium", "pricingNotes": "MCP server itself is free; Actor runs are billed on Apify plans: Free $0 with $5/month usage credit ($0.20 per compute unit), Starter $19/mo, Scale $199/mo ($0.16/CU), Business $999/mo ($0.13/CU), 10% off annual (https://apify.com/pricing).", "priceSummary": "$1 / call", "where": "both", "x402": { "level": "yes", "evidence": "AGI (agi.apify.com) sells a prepaid, spend-capped Apify token over x402 (USDC on Base, or USDC or USDT on Solana) or MPP (Tempo or Solana), minimum $1, currently valid for 14 days with unused balance not refunded, usable as `Authorization: Bearer` against mcp.apify.com and api.apify.com for any Actor. Direct x402 on `mcp.apify.com?payment=x402` signs a $1.00 USDC prepayment on Base, covers Pay Per Event Actors only (not Standby), and refunds unused balance after 60 minutes of inactivity (https://agi.apify.com/; https://github.com/apify/apify-mcp-server#-agentic-payments; https://apify.com/pricing, checked 2026-10-04).", "endpoints": [ { "url": "https://agi.apify.com/protocols/x402/prepaid-tokens?amount=1\u0026currency=usd", "priceUsd": 1, "network": "eip155:8453" }, { "url": "https://mcp.apify.com?payment=x402", "priceUsd": 1, "network": "eip155:8453" } ] }, "toolCount": 35, "popularity": { "githubStars": 8600, "npmWeekly": 15257, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/apify/apify-mcp-server#readme", "registryName": "com.apify/apify-mcp-server", "capabilities": [ "scraping.actors", "web.crawl" ], "tags": [ "official", "hosted", "local", "open-source", "x402", "aggregator" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 76.5, "grade": "BB", "agentReady": true, "rank": 28, "ranked": true, "rankOf": 950, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 92, "maintenance": 95, "payments": 95, "reliability": 65, "schema": 92, "security": 62, "transparency": 86 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-04" }, "negative": -5, "negativeNotes": [ "-3: v0.16.0 on 2026-09-17 renamed get-actor-log to get-actor-run-log with no deprecation period, and the old name is now ignored without an error. It was flagged as breaking in the changelog on release day, so the lowest deduction (https://github.com/apify/apify-mcp-server/blob/master/CHANGELOG.md).", "-2: GHSA-6gr2-qh89-hxwm (CVE-2026-50143, CVSS 8.1, High). Versions before 0.10.11 built an Actor's MCP URL by joining strings, so a malicious Actor's webServerMcpPath could send the user's Apify token to another host. Fixed in 0.10.11 on 28 May 2026 and published as a GitHub advisory, about four months old, so 2 points rather than the full deduction for an exfiltration path. The Moderate GHSA-jwp7-wg77-3w9v (CVE-2026-46341), a fetch-apify-docs allowlist bypass fixed in 0.9.21 on 4 May 2026, wasn't deducted (https://github.com/apify/apify-mcp-server/security/advisories/GHSA-6gr2-qh89-hxwm; https://github.com/apify/apify-mcp-server/security/advisories/GHSA-jwp7-wg77-3w9v)." ], "verdict": "x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.", "bestFor": "Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.", "strengths": [ "x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors", "12 tools by default out of 35, `?tools=` to pick categories, and readOnly, destructive and idempotent hints on every tool", "Scoped API tokens with expiry and a 24-hour rotation overlap, plus OAuth on the hosted server", "18 releases between 21 July and 30 September 2026, with breaking changes flagged in the changelog", "Free plan with $5 of monthly usage and no card" ], "weaknesses": [ "API and Actor runs timed out for about 12 hours on 21 and 22 July 2026", "No prompt-injection guidance for scraped content or third-party Actor READMEs", "Telemetry and Sentry on by default", "Direct x402 and Skyfire cover Pay Per Event Actors only, not Standby Actors", "No SLA published for any self-serve plan" ], "agentNotes": [ "Call fetch-actor-details before call-actor to get the input schema and the price", "Use apify--web-fetch for one known URL and apify--rag-web-browser for search and read", "Read results with get-dataset-items and set `fields` and `limit`. The default is 20 rows", "Buy an AGI token for anything that isn't a Pay Per Event Actor, since direct `?payment=x402` refuses the rest. Tokens last 14 days and unused balance isn't refunded", "Ask for `get-actor-run-log`, not `get-actor-log`. The old name is ignored without an error" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 76.5 } ], "editorialScores": { "ergonomics": 92, "maintenance": 95, "payments": 95, "reliability": 65, "schema": 92, "security": 62, "transparency": 75 }, "provenanceScore": 96 }, "connect": { "claudeCode": "claude mcp add --transport http apify https://mcp.apify.com --header \"Authorization: Bearer ${APIFY_TOKEN}\"", "config": { "mcpServers": { "apify": { "headers": { "Authorization": "Bearer ${APIFY_TOKEN}" }, "url": "https://mcp.apify.com" } } }, "x402": "curl -s -i -X POST 'https://agi.apify.com/protocols/x402/prepaid-tokens?amount=1\u0026currency=usd'\n# 402 -\u003e pay with PAYMENT-SIGNATURE (USDC, eip155:8453) -\u003e token in response\n# then: Authorization: Bearer \u003cprepaid token\u003e against https://mcp.apify.com" }, "letme": { "capability": "https://letme.dev/scraping.actors", "tool": "https://letme.dev/apify-mcp" }, "area": "web-data", "unitPrices": [ { "item": "Compute unit, pay as you go", "unit": "compute-unit", "usd": 0.2 } ], "provenance": { "legalEntity": "Apify Technologies s.r.o.", "domain": "apify.com", "domainRegistered": "2009-06-02", "endpointOnVendorDomain": true, "terms": "https://docs.apify.com/legal/general-terms-and-conditions", "privacy": "https://docs.apify.com/legal/privacy-policy", "statusPage": "https://status.apify.com", "changelog": "https://github.com/apify/apify-mcp-server/releases", "securityTxt": "valid", "checked": "2026-10-04", "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/apify-mcp.json", "live": { "slug": "apify-mcp", "probe": { "target": "https://mcp.apify.com", "method": "mcp-initialize", "lastAt": "2026-10-10T03:53:18.799362111Z", "lastOk": true, "lastStatus": 401, "lastMs": 252, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.88, "p50ms24h": 258, "p95ms24h": 368, "samples24h": 249, "samples30d": 3430, "days": [ { "date": "2026-09-27", "probes": 132, "ok": 132 }, { "date": "2026-09-28", "probes": 285, "ok": 284 }, { "date": "2026-09-29", "probes": 286, "ok": 286 }, { "date": "2026-09-30", "probes": 286, "ok": 286 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 247 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 271 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 267 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.apify.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:57:59.70063675Z" }, "versions": [ { "registry": "github", "name": "apify/actors-mcp-server", "version": "v0.17.1", "released": "2026-09-30", "seenAt": "2026-10-01T13:17:39.020905395Z" }, { "registry": "github", "name": "apify/apify-mcp-server", "version": "v0.17.4", "released": "2026-10-07", "seenAt": "2026-10-09T16:39:51.399264694Z" }, { "registry": "mcp-registry", "name": "com.apify/apify-mcp-server", "version": "0.17.4", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@apify/actors-mcp-server", "version": "0.17.4", "seenAt": "2026-10-09T16:39:50.973195864Z" } ], "githubStars": 10262, "npmWeekly": 37446, "securityTxt": { "url": "https://apify.com/.well-known/security.txt", "state": "valid", "expires": "2035-01-01T00:00:00.000Z", "checkedAt": "2026-10-09T15:39:20.192411299Z" }, "domain": { "domain": "apify.com", "registered": "2009-06-02", "source": "https://rdap.verisign.com/com/v1/domain/apify.com", "checkedAt": "2026-10-04T13:08:53.704775538Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/apify/apify-mcp-server/master/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-09T18:44:57.06988591Z", "changedAt": "2026-10-08T18:23:57.629359609Z", "fingerprint": "e3263a1bd63c" }, { "url": "https://apify.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:32:35.89770665Z", "changedAt": "2026-10-09T18:32:35.89770665Z", "fingerprint": "247eca42cbc4" }, { "url": "https://docs.apify.com/legal/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-09T18:36:33.957291797Z", "changedAt": "2026-10-03T15:31:21.810791643Z", "fingerprint": "9c93506c6ab7" }, { "url": "https://docs.apify.com/legal/general-terms-and-conditions", "kind": "terms", "status": 304, "checkedAt": "2026-10-09T18:36:31.772531131Z", "changedAt": "2026-10-03T15:31:19.543950962Z", "fingerprint": "ba43983c7610" } ], "mcpTools": { "url": "https://mcp.apify.com", "checkedAt": "2026-10-09T21:40:18.507509212Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:37.935476956Z" }, "updatedAt": "2026-10-10T03:57:59.70063675Z" } }, "answer": "Apify MCP Server scores 76.5 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability.", "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", "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-05", "graded": true, "anchor": { "graded": true, "score": 69.7, "grade": "B", "agentReady": false, "rank": 175, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 77, "payments": 40, "reliability": 85, "schema": 85, "security": 55, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "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, so cost per request isn't known before the site is assigned one, and no dated API changelog was found.", "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 one unauthenticated request there on 9 October 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)" ], "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": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "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": 73 }, "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": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zyte.json", "live": { "slug": "zyte", "probe": { "target": "https://api.zyte.com/v1/extract", "method": "get", "lastAt": "2026-10-10T03:53:51.139717524Z", "lastOk": true, "lastStatus": 405, "lastMs": 347, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 351, "p95ms24h": 440, "samples24h": 209, "samples30d": 209, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.zyte.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:53.12518428Z" }, "versions": [ { "registry": "pypi", "name": "scrapy-zyte-api", "version": "0.36.0", "released": "2026-08-20", "seenAt": "2026-10-09T17:30:10.201520445Z" }, { "registry": "pypi", "name": "zyte-api", "version": "0.11.0", "released": "2026-07-23", "seenAt": "2026-10-09T17:30:10.012038183Z" } ], "githubStars": 30, "pypiWeekly": 43358, "securityTxt": { "url": "https://zyte.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:43.251731951Z" }, "llmsTxt": { "url": "https://docs.zyte.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:03:05.632872525Z" }, "pages": [ { "url": "https://docs.zyte.com/zyte-api/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:38:53.393499232Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5864dd4dc492" }, { "url": "https://www.zyte.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:56:06.820819936Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d8f74b8aaa20" }, { "url": "https://www.zyte.com/terms-policies/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:56:09.293782547Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "eedc33ef77a7" }, { "url": "https://www.zyte.com/terms-policies/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:56:11.113760637Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ec0a2dae6702" } ], "updatedAt": "2026-10-10T03:58:53.12518428Z" } }, "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Apify", "b": "Zyte Group Limited", "name": "Vendor" }, { "a": "https://mcp.apify.com", "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": "yes, from $1/call", "b": "no", "name": "x402" }, { "a": "MIT", "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": "35", "b": "34", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "com.apify/apify-mcp-server", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-30", "b": "2026-10-05", "name": "Last release" }, { "a": "2026-07-09", "b": "2026-09-22", "name": "Terms last updated" }, { "a": "2026-07-09", "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": "not found in the text", "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": "8.6k stars, 15k npm/wk", "b": "42k PyPI/wk", "name": "Popularity" }, { "a": "3.4/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Apify MCP Server scores 76.5 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability.", "question": "Which is better for AI agents, Apify MCP Server or Zyte API?" }, { "answer": "Both take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.", "question": "Do Apify MCP Server and Zyte API need an API key?" }, { "answer": "Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Zyte API at https://api.zyte.com/v1/extract.", "question": "Can an agent call Apify MCP Server and Zyte API without installing anything?" }, { "answer": "Apify MCP Server is open source (MIT). No open-source release is listed for Zyte API.", "question": "Are Apify MCP Server and Zyte API open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 92 against 85", "Agent ergonomics, 92 against 72", "Security \u0026 auth, 62 against 55", "Payments \u0026 pricing, 95 against 40", "Maintenance \u0026 community, 95 against 77", "Transparency \u0026 trust, 86 against 66" ], "also": [ "Agent-ready, a grade of BB or better", "An agent can pay per call over x402, with no account", "Runs on your own machine", "Open source" ], "goodFor": "Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.", "slug": "apify-mcp", "watchFor": "API and Actor runs timed out for about 12 hours on 21 and 22 July 2026" }, { "aheadOn": [ "Reliability, 85 against 65" ], "also": [ "Free to start without a card", "No incidents deducted, where Apify MCP Server loses 5 points for them" ], "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" } ], "job": { "capability": "web.scrape", "name": "Scraping" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader.json", "title": "Apify MCP Server vs Jina Reader", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper.json", "title": "Apify MCP Server vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.json", "title": "Apify MCP Server vs Scrape.do", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant.json", "title": "Apify MCP Server vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.json", "title": "Apify MCP Server vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.json", "title": "Apify MCP Server vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows.json", "title": "Apify MCP Server vs ZenRows", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows" }, { "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/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/olostep-vs-zyte.json", "title": "Olostep vs Zyte API", "url": "https://www.anchorterminal.com/compare/olostep-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/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/zenrows-vs-zyte.json", "title": "ZenRows vs Zyte API", "url": "https://www.anchorterminal.com/compare/zenrows-vs-zyte" }, { "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/apify-mcp-vs-bright-data.json", "title": "Apify MCP Server vs Bright Data", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot.json", "title": "Apify MCP Server vs Diffbot", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp.json", "title": "Apify MCP Server vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-olostep.json", "title": "Apify MCP Server vs Olostep", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.json", "title": "Apify MCP Server vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless.json", "title": "Apify MCP Server vs Scrapeless", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.json", "title": "Apify MCP Server vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly.json", "title": "Apify MCP Server vs Scrapfly", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.json", "title": "Apify MCP Server vs Spider", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud" } ], "scores": [ { "apify-mcp": 65, "by": 20, "edge": "zyte", "key": "reliability", "name": "Reliability", "weight": 16, "zyte": 85 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "apify-mcp": 92, "by": 7, "edge": "apify-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zyte": 85 }, { "apify-mcp": 92, "by": 20, "edge": "apify-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zyte": 72 }, { "apify-mcp": 62, "by": 7, "edge": "apify-mcp", "key": "security", "name": "Security \u0026 auth", "weight": 14, "zyte": 55 }, { "apify-mcp": 95, "by": 55, "edge": "apify-mcp", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zyte": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "apify-mcp": 95, "by": 18, "edge": "apify-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zyte": 77 }, { "apify-mcp": 86, "by": 20, "edge": "apify-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zyte": 66 } ], "summary": "Apify MCP Server scores 76.5 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability. Both do scraping. Apify MCP Server accepts x402. Zyte API doesn't.", "verdicts": { "apify-mcp": "x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.", "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, so cost per request isn't known before the site is assigned one, and no dated API changelog was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte", "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.md", "slim": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.min.md" }, "markdown": "Apify MCP Server scores 76.5 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability. Both do scraping. Apify MCP Server accepts x402. Zyte API doesn't.\n\n- Apify MCP Server: grade BB, 76.5/100, rank #28 of 950. Markdown https://www.anchorterminal.com/tools/apify-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/apify-mcp.json\n- Zyte API: grade B, 69.7/100, rank #175 of 950. 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 167 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Apify MCP Server (BB)\n\nGood for: Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.\n\nAhead on:\n- Schema \u0026 documentation, 92 against 85\n- Agent ergonomics, 92 against 72\n- Security \u0026 auth, 62 against 55\n- Payments \u0026 pricing, 95 against 40\n- Maintenance \u0026 community, 95 against 77\n- Transparency \u0026 trust, 86 against 66\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- An agent can pay per call over x402, with no account\n- Runs on your own machine\n- Open source\n\nWatch for: API and Actor runs timed out for about 12 hours on 21 and 22 July 2026\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 65\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Apify MCP Server loses 5 points for them\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## Score by category\n\n| Category | Weight | Apify MCP Server | Zyte API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 85 | Zyte API +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 85 | Apify MCP Server +7 |\n| Agent ergonomics | 13% (16.2 this run) | 92 | 72 | Apify MCP Server +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 55 | Apify MCP Server +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 95 | 40 | Apify MCP Server +55 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 95 | 77 | Apify MCP Server +18 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 86 | 66 | Apify MCP Server +20 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **76.5 · BB** | **69.7 · B** | |\n\n## Facts side by side\n\n| Fact | Apify MCP Server | Zyte API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Apify | Zyte Group Limited |\n| Hosted endpoint | `https://mcp.apify.com` | `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 | yes, from $1/call | no |\n| Licence | MIT | 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 | 35 | 34 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `com.apify/apify-mcp-server` | not listed |\n| Last release | 2026-09-30 | 2026-10-05 |\n| Terms last updated | 2026-07-09 | 2026-09-22 |\n| Privacy policy last updated | 2026-07-09 | 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 | not found in the text | 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 | 8.6k stars, 15k npm/wk | 42k PyPI/wk |\n| Agent reviews | 3.4/5 (8) | none |\n\n## Verdicts\n\n**Apify MCP Server.** x402 on Apify's own domains, a prepaid token from agi.apify.com for any Actor and per-run payment on mcp.apify.com for Pay Per Event Actors. API and Actor runs timed out for about 12 hours on 21 and 22 July 2026.\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, so cost per request isn't known before the site is assigned one, and no dated API changelog was found.\n\n## Before you call either\n\n### Apify MCP Server\n\n1. Call fetch-actor-details before call-actor to get the input schema and the price\n2. Use apify--web-fetch for one known URL and apify--rag-web-browser for search and read\n3. Read results with get-dataset-items and set `fields` and `limit`. The default is 20 rows\n4. Buy an AGI token for anything that isn't a Pay Per Event Actor, since direct `?payment=x402` refuses the rest. Tokens last 14 days and unused balance isn't refunded\n5. Ask for `get-actor-run-log`, not `get-actor-log`. The old name is ignored without an error\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## Questions\n\n### Which is better for AI agents, Apify MCP Server or Zyte API?\n\nApify MCP Server scores 76.5 (BB) on agent readiness against Zyte API's 69.7 (B), and leads in 6 of 7 scored categories. Zyte API leads on reliability.\n\n### Do Apify MCP Server and Zyte API need an API key?\n\nBoth take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.\n\n### Can an agent call Apify MCP Server and Zyte API without installing anything?\n\nYes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Zyte API at https://api.zyte.com/v1/extract.\n\n### Are Apify MCP Server and Zyte API open source?\n\nApify MCP Server is open source (MIT). 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/apify-mcp-vs-zyte.json, and with the fewest tokens: https://www.anchorterminal.com/compare/apify-mcp-vs-zyte.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"apify-mcp\", \"b\": \"zyte\"}`. From a terminal: `anchor compare apify-mcp zyte`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/apify-mcp.json and https://www.anchorterminal.com/api/v1/tools/zyte.json\n\n## Other comparisons with Apify MCP Server or Zyte API\n\n- [Apify MCP Server vs Jina Reader](https://www.anchorterminal.com/compare/apify-mcp-vs-jina-reader.md)\n- [Apify MCP Server vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/apify-mcp-vs-oxylabs-web-scraper.md)\n- [Apify MCP Server vs Scrape.do](https://www.anchorterminal.com/compare/apify-mcp-vs-scrape-do.md)\n- [Apify MCP Server vs ScrapingAnt](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingant.md)\n- [Apify MCP Server vs ScrapingBee](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingbee.md)\n- [Apify MCP Server vs Scrapingdog](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapingdog.md)\n- [Apify MCP Server vs ZenRows](https://www.anchorterminal.com/compare/apify-mcp-vs-zenrows.md)\n- [Bright Data vs Zyte API](https://www.anchorterminal.com/compare/bright-data-vs-zyte.md)\n- [Jina Reader vs Zyte API](https://www.anchorterminal.com/compare/jina-reader-vs-zyte.md)\n- [Olostep vs Zyte API](https://www.anchorterminal.com/compare/olostep-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- [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- [ZenRows vs Zyte API](https://www.anchorterminal.com/compare/zenrows-vs-zyte.md)\n- [Diffbot vs Zyte API](https://www.anchorterminal.com/compare/diffbot-vs-zyte.md)\n- [Apify MCP Server vs Bright Data](https://www.anchorterminal.com/compare/apify-mcp-vs-bright-data.md)\n- [Apify MCP Server vs Diffbot](https://www.anchorterminal.com/compare/apify-mcp-vs-diffbot.md)\n- [Apify MCP Server vs Firecrawl MCP](https://www.anchorterminal.com/compare/apify-mcp-vs-firecrawl-mcp.md)\n- [Apify MCP Server vs Olostep](https://www.anchorterminal.com/compare/apify-mcp-vs-olostep.md)\n- [Apify MCP Server vs ScrapeGraphAI](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapegraphai.md)\n- [Apify MCP Server vs Scrapeless](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapeless.md)\n- [Apify MCP Server vs ScraperAPI](https://www.anchorterminal.com/compare/apify-mcp-vs-scraperapi.md)\n- [Apify MCP Server vs Scrapfly](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapfly.md)\n- [Apify MCP Server vs Spider](https://www.anchorterminal.com/compare/apify-mcp-vs-spider-cloud.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Apify MCP Server vs Zyte API", "url": "" } ], "description": "Apify scores 76.5 (BB) to Zyte's 69.7 (B) for scraping. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Apify MCP Server BB 76.5", "Zyte API B 69.7", "scores" ], "h1": "Apify MCP Server vs Zyte API", "image": "https://www.anchorterminal.com/assets/og/compare-apify-mcp-vs-zyte.png", "path": "/compare/apify-mcp-vs-zyte", "published": "2026-10-01", "section": "tools", "title": "Apify vs Zyte for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-zyte" }, "tokens": { "markdown": 2750, "slim": 830 }, "version": 1 }