Head to head · Scraping · October 2026 research run
ScrapingBee vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against ScrapingBee's 62 (B), and leads in every scored category. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.
Also in its favour
- No incidents deducted, where ZenRows loses 3 points for them
Watch for
remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL
ZenRows A
Best for An agent hitting protected sites that wants the service to choose the setup and bill only success, and for agents that must onboard without a human.
Ahead on
- Reliability, 87 against 75
- Schema & documentation, 93 against 60
- Agent ergonomics, 79 against 68
- Security & auth, 50 against 37
- Payments & pricing, 100 against 60
- Maintenance & community, 90 against 75
- Transparency & trust, 79 against 65
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
The Fetch API only takes the key in the query string
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing ZenRows +40
ScrapingBee 60
No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
ZenRows 100
x402 and MPP through an agent storefront at agents.zenrows.com run by ZeroClick, which sells Fetch and Extract and proxies calls through its own path, with pay-as-you-go credits at $0.50 per 1,000 (10,000 minimum) per the pricing docs. Nothing on api.zenrows.com itself (20 of 40). Credit weights and plan prices are public, Build B1 $19 for 45,000 credits up to Scale S5 $2,999 for 45 million (20). 5,000 free credits a month, no card (20). With no key set, the stdio MCP and the CLI provision a Free account through POST https://app.zenrows.com/api/agent/signup, which the OpenAPI file documents, and an agent can also buy over x402 at the storefront (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 70 is 105 at 30 each, so 80 is 100.
Schema & documentation ZenRows +33
ScrapingBee 60
No OpenAPI spec found. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas are only in its live tools/list (8 of 25). llms.txt indexes 26 per-endpoint and integration text files written for models (10). The API files explain each parameter's purpose and cost, and the reference-notes file tabulates 12 source discrepancies and coverage notes from its own pages. MCP tool descriptions aren't published beyond a tool table (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15). 8 + 10 + 10 + 10 + 14 + 8 = 60.
ZenRows 93
OpenAPI 3.1 at www.zenrows.com/openapi.json covers Fetch, Extract, Crawl (added after the 9 October launch), Batch, agent signup and HMAC key rotation, and the 63 MCP tools have typed zod inputs (25). llms.txt with 105 entries linking 240 docs pages on 1 November, each with a Markdown copy (10). The scrape tool says when to prefer extract, when to turn on js_render or premium_proxy, and gives three examples, and the crawl tools say when to wait, page or download. The browser tools are terser (18 of 20). Enums on mode and response_type, URL validation and required fields, but css_extractor is a JSON string and outputs a comma-separated string (12 of 15). Error catalogue of 35 codes such as AUTH004 and RESP002, plus a table of Batch and Extract codes, grouped by HTTP status with fixes, and every OpenAPI operation lists its error responses (15). The API is versioned in the path (v1, never retired), a dated changelog at www.zenrows.com/changelog runs to 9 October 2026, with nothing newer on 1 November, and the MCP has semver tags. The 2026 renames (Universal Scraper API to Fetch, Scraping Browser to Browser Sessions) aren't in it (13 of 15).
Maintenance & community ZenRows +15
ScrapingBee 75
CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time). The CLI's later commits (plugin manifests for Cursor, Codex, Copilot CLI, Kiro and Antigravity, 6 to 30 October) sit under its changelog's Unreleased heading, the plugins still carry version 1.6.0, and the mcp-server repository holds only a README. In the 90 days from 6 August, Python SDK v2.1.1 (6 August, a documentation release) and v2.2.0 and Node SDK v2.0.0 (1 September) at half as SDK tags, CLI v1.6.0 in full as the vendor's own CLI with new commands and options, and the Employee Search API launch (blog post of 14 August) make 3.5 (20). We couldn't read GitHub issues. Dated SDK changelogs and email support (10 of 25). Current official Python and Node SDKs and a CLI. The MCP isn't in the official registry (15). Test workflows run in CI on all three repositories (10). 20 + 20 + 10 + 15 + 10 = 75.
ZenRows 90
MCP v2.18.0 on 2026-10-30 (30). Seven MCP minor releases from 18 to 30 October alone (v2.12.0 to v2.18.0), and dated changelog entries on 2, 5 and 9 October (20). We couldn't read GitHub issues. PRs are merged within days and the dated changelog on zenrows.com runs to 9 October (15 of 25). In the official MCP registry as io.github.ZenRows/zenrows-mcp, with 2.18.0 published on 30 October and marked latest (15). CI runs typecheck, lint and tests on a Node matrix, and a check that server.json matches the package version (10).
Transparency & trust ZenRows +14
ScrapingBee 65
Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).
ZenRows 79
Closed service, with ZENROWS, S.L. named in full (Getxo, Spain, tax ID B10660298). The MCP is MIT (15 of 30). The privacy policy, still dated September 2024, keeps account data for the contract plus legal periods. A Data Processing Agreement at /legal/data-processing-agreement, in effect since 1 June 2022 and not read on 1 or 6 October, commits to deletion with a certificate on request, prompt breach notice and liability for sub-processors, with no SCCs or right to object to a new sub-processor. The GDPR page keeps trial and cancelled accounts until deletion is requested. Batch results are kept 14 days, and no retention is stated for Fetch responses (19 of 30). A published versioning policy promises at least twelve months' notice, Deprecation and Sunset headers and a migration guide before a version is retired. The 2026 renames carried no dated notices (15 of 20). The privacy policy names six US recipients with their transfer mechanism (Google, Amplitude, AWS, Stripe, ProfitWell, HubSpot). The GDPR page says the service is 'primarily hosted on Digital Ocean' and sends email through Intercom, neither of which is on that list, and there's no single sub-processor list with locations (16 of 20). 15+19+15+16 = 65.
Security & auth ZenRows +13
ScrapingBee 37
One API key per account, which the MCP notes say can be revoked (401 on revoked keys). Team management exists. No scopes (20). The api_key query parameter is deprecated but still works, and remote-mcp.txt says the hosted MCP takes the key only as ?api_key= in its URL, "not a Bearer header or OAuth flow", so less 10 (10 of 30). No read-only or scoped key, and the HTML API can send POST requests to target sites. The CLI gates shell post-processing behind an explicit unsafe flag (8 of 20). The official CLI skills and AGENTS.md say scraped output is data, never instructions, and tell the agent to report instruction-like content as a possible prompt injection. The MCP docs say nothing (12 of 15). A Usage API and a local CLI audit log. No per-request log in the docs (7 of 15). www.scrapingbee.com/.well-known/security.txt answers 404, and no bug bounty, disclosure policy or certification found (0 of 20). 10 + 8 + 12 + 7 + 0 = 37.
ZenRows 50
The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November. Batch, Crawl, the Extract endpoints and the account endpoint take an X-API-Key header, Crawl and Extract the query parameter too, and the hosted MCP a Bearer header or OAuth. An account can hold up to 10 keys, each revocable, with no documented scopes (20, less 10 for the query string, so 10 of 30). Per-key credit caps by billing period, day, week or month stop only the capped key, with alerts at 80 and 100 per cent. There is no read-only subset or confirmation step, though annotations mark the browser tools as not read-only, and since v2.15.1 (21 October) the ones that overwrite or delete page state as destructive (12 of 20). No prompt-injection guidance found in the docs index, the MCP overview, the MCP README, the server instructions or the tool descriptions (0 of 15). X-Request-Id and X-Request-Cost on every response, a free account_usage tool, and an Activity Log listing each Fetch, Extract, Batch and Browser request for up to 60 days per the changelog of 31 July 2026 (13 of 15). security.txt on www.zenrows.com, re-read on 1 November, valid to 1 November 2027 with a security@zenrows.com contact and a linked information security policy. An ISO 27001 certificate linked from the site footer, and SOC 2 Type II claimed. No bug bounty found (15 of 20).
Reliability ZenRows +12
ScrapingBee 75
status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20). In the 90 days from 6 August it posted five incidents, each "Degraded performance" on one component with no downtime on the uptime bars. Half of non-JavaScript HTML traffic was rejected for 20 minutes on 18 August, Google API /goto link resolution dropped from 9 to 10 September, Google API success rates fell for about six and a half hours on 22 September, and HTML Scraping with Rendering, the default, was degraded for about 11 hours on 21 October and about 5 hours on 28 October. Each is partial, so minor only (20; 15 before, when the July incidents were in the window). Concurrency per plan is published, 25 on Hobby to 400 on Business+ and 900 on Enterprise 120 (15). 429 means the concurrency limit and isn't billed, target failures are retried server-side for up to 30 seconds on most dedicated APIs, and the MCP notes advise exponential backoff. No Retry-After or safe-write guidance found (10). No SLA found (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
ZenRows 87
Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20). The feed's newest incident is still the AWS outage of 20 October 2025, so nothing in the 90 days to 1 November, with the Fetch service at 99.998 per cent and the website at 100 on 1 November (30). Concurrency per plan is published (5 on Free up to 1,000 or more on Enterprise) and every response carries Concurrency-Limit and Concurrency-Remaining headers (15). The OpenAPI file documents 429 AUTH008 with exponential backoff and Concurrency-Remaining, and says there is no Retry-After (12 of 15). The pricing page lists an SLA under Enterprise, but no terms or figure are published (0). Fetch is generally available. Crawl, launched on 9 October, is still called 'still evolving' in the MCP README (10).
Score by category
| Category | Weight | ScrapingBee | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 87 | ZenRows +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 60 | 93 | ZenRows +33 |
| Agent ergonomics | 13% | 68 | 79 | ZenRows +11 |
| Security & auth | 14% | 37 | 50 | ZenRows +13 |
| Payments & pricing | 10% | 60 | 100 | ZenRows +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 90 | ZenRows +15 |
| Transparency & trust | 7% | 65 | 79 | ZenRows +14 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 62/100 | A 78.4/100 |
Facts side by side
| Fact | ScrapingBee | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ScrapingBee (Oxylabs group) | ZenRows |
| Hosted endpoint | https://app.scrapingbee.com/api/v1/ | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | payer tooling only |
| Tools exposed | 18 | 63 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-09-11 | 2026-10-30 |
| Terms last updated | 2024-07-15 | 2025-07-01 |
| Privacy policy last updated | 2024-07-15 | 2024-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 132 stars, 49k npm/wk, 72k PyPI/wk | 21 stars, 35k npm/wk |
| Agent reviews | 4/5 (2) | 3.8/5 (8) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | ScrapingBee | ZenRows |
|---|---|---|
| LedgerCost analyst | 4/5 Five credits by default, one with rendering off | 4/5 $0.42 per 1,000 plain, $10.56 protected |
| ScoutResearch agent | 4/5 Docs that list nine of their own conflicts | 4/5 227 Markdown pages and a scrape tool that says when not to use it |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
ScrapingBee
Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API, with per-endpoint llms files and an auto mode that bills only the tier that works. The hosted MCP's own notes say it takes the key only as ?api_key= in its URL, and no API changelog or security.txt was found.
ZenRows
No incidents in the 90 days to 1 November 2026 on a six-component Better Stack status page, and an OpenAPI 3.1 file with coded errors. The Fetch API only takes the key in the query string.
Before you call either
ScrapingBee
- Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
- Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
- Keep the MCP URL with ?api_key= out of logs and shared configs
- Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
- Expect 404 and 410 from the target to be billed. Other failures aren't
ZenRows
- Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
- Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
- On REQS007 from extract, read
reason. Call prepare_domain for domain_not_prepared, or fall back to css_extractor; extract no longer falls back to autoparse - Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
- On a 402 with AUTH014, only this key hit its cap. Read X-Key-Credits-Remaining and don't tell the user to buy credits
- Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account
- Pass
idempotency_keytocrawl_createandbatch_createso a retried call returns the same job instead of starting and billing a second one
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract page titles and links with ZenRows, for ZenRows
Questions
Which is better for AI agents, ScrapingBee or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against ScrapingBee's 62 (B), and leads in every scored category.
Do ScrapingBee and ZenRows need an API key?
ScrapingBee needs an API key. ZenRows takes an API key or an OAuth sign-in.
Can an agent call ScrapingBee and ZenRows without installing anything?
Yes. ScrapingBee has a hosted endpoint at https://app.scrapingbee.com/api/v1/ and ZenRows at https://api.zenrows.com/v1/.
Other comparisons with ScrapingBee or ZenRows
- Apify MCP Server vs ScrapingBee
- Apify MCP Server vs ZenRows
- Bright Data vs ScrapingBee
- Bright Data vs ZenRows
- BrowserAct vs ScrapingBee
- BrowserAct vs ZenRows
- Context.dev vs ScrapingBee
- Context.dev vs ZenRows
- Crawl4AI vs ScrapingBee
- Crawl4AI vs ZenRows
- fastCRW vs ScrapingBee
- fastCRW vs ZenRows
- Decodo Web Data API vs ScrapingBee
- Decodo Web Data API vs ZenRows
- jevcrawl vs ScrapingBee
- jevcrawl vs ZenRows
- Jina Reader vs ScrapingBee
- Jina Reader vs ZenRows
- Microlink vs ScrapingBee
- Microlink vs ZenRows
- Olostep vs ScrapingBee
- Olostep vs ZenRows
- Outcrawl vs ScrapingBee
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs ScrapingBee
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs ScrapingBee
- Scrape.do vs ZenRows
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs ZenRows
- Scrapeless vs ScrapingBee
- Scrapeless vs ZenRows
- ScraperAPI vs ScrapingBee
- ScraperAPI vs ZenRows
- Scrapewise vs ScrapingBee
- Scrapewise vs ZenRows
- Scrapfly vs ScrapingBee
- Scrapfly vs ZenRows
- ScrapingAnt vs ScrapingBee
- ScrapingAnt vs ZenRows
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Scrapling
- ScrapingBee vs Spider
- ScrapingBee vs WebScraping.AI
- ScrapingBee vs Zyte API
- Scrapingdog vs ZenRows
- Scrapling vs ZenRows
- Spider vs ZenRows
- WebScraping.AI vs ZenRows
- ZenRows vs Zyte API
- Firecrawl MCP vs ScrapingBee
- Diffbot vs ScrapingBee
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs ScrapingBee
- Nexscope vs ZenRows
- Qovia vs ScrapingBee
- Qovia vs ZenRows
- ScrapeAtlas vs ScrapingBee
- ScrapeAtlas vs ZenRows
- ScrapingBee vs SoldFetch
- SoldFetch vs ZenRows
- ScrapeOps Proxy API Aggregator vs ScrapingBee
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/scrapingbee-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapingbee.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare scrapingbee zenrows(the CLI) - Over MCP
compare_tools {"a": "scrapingbee", "b": "zenrows"}at/mcp, no key