Head to head · Scraping · October 2026 research run
Scrapfly vs ScrapingBee
Scrapfly scores 77 (BB) on agent readiness against ScrapingBee's 62 (B), and leads in 6 of 7 scored categories. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Scrapfly BB
Best for An agent that needs scrape, screenshot, extraction, crawl and a hosted browser from one key, with errors it can branch on.
Ahead on
- Reliability, 85 against 75
- Schema & documentation, 95 against 60
- Agent ergonomics, 80 against 68
- Security & auth, 75 against 37
- Maintenance & community, 84 against 75
- Transparency & trust, 75 against 65
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
The open-source MCP server registers 62 tools at once, a heavy tools/list
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 Scrapfly loses 3 points for them
Watch for
remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL
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.
Security & auth Scrapfly +38
Scrapfly 75
OAuth 2 on the hosted MCP with dashboard revocation, open to all plans. API keys are per project, live or test, and since 15 April 2026 can be restricted to products (30). The canonical API form puts the key in the key query parameter and the MCP also accepts ?key=, so less 10 (20 of 30). Product-restricted keys, confirm=true on every mutating vault and alert tool, info_api_key off in server-key mode, and the self-hosted HTTP server binds loopback by default. Since v1.4.0 Cloud Browser sessions are scoped to the API key that opened them (15 of 20). The source gates mutating vault tools behind a preview step because prompt injection can reach them and redacts keys from CDP URLs. We found no user-facing guidance on untrusted page content (8 of 15). Monitoring shows every call as a log with its error, credit cost line by line and Unblocker state, with replay, per the 24 October release notes, as well as per-domain metrics and alerting. The 1 October check couldn't confirm per-request logs (15, was 10). security.txt valid until 30 April 2027, SOC 2 Type II, ISO 27001 and HIPAA claims on the pricing page, and a public SOC 3 report since 21 April 2026. No bug bounty found (17 of 20). 20+15+8+15+17 = 75.
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.
Schema & documentation Scrapfly +35
Scrapfly 95
A Swagger reference per the 30 September check, and the MCP server exposes it as a web_scraping_openapi_specification resource. Every MCP tool has JSON Schema inputs generated from typed Go structs (25). llms.txt and Markdown twins such as pricing.md per the 30 September check. robots.txt still disallows /docs/llms.txt and the .md twins for crawlers it doesn't name, so they weren't re-read on 1 November (10). Descriptions say when to use a tool and when to switch, for example web_get_page falls back to web_scrape for tuning and to cloud_browser_open for interaction. A few are long and steer the model's next step (17 of 20). Typed inputs with enums, for example the vault service discriminator, and required fields (13 of 15). Error catalogue of 100+ ERR:: codes, each with HTTP status, retryable and billed flags and its own doc link (15). Dated release notes, newest 26 October 2026 (15). 25+10+17+13+15+15 = 95.
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.
Agent ergonomics Scrapfly +12
Scrapfly 80
The open-source server registers 62 tools by default in v1.4.0 (5 web scraping, 2 account, 9 Cloud Browser sessions, 17 page interaction, 2 WebMCP, 15 credential vault, 12 alerts), all at once, and the docs list a smaller core. There's a code path to mount interaction tools per session, but registration is always-on for clients that don't refetch. On the API side, format=markdown and the extraction API keep responses small, and since v1.4.0 the scrape tools report api_cost and cost_details (10 of 25). Output format, extraction templates, crawler limits and 100-URL batches (15 of 20). Error codes an agent can branch on, with retryable and billed flags (20). Tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and mutating vault and alert tools need confirm=true after a preview (20). web_get_page works with a URL alone, and official SDKs exist for Python, TypeScript, Go and Rust (15). 10+15+20+20+15 = 80.
ScrapingBee 68
18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15).
Reliability Scrapfly +10
Scrapfly 85
scrapfly.io/status answers with Statuspage's status JSON, which names its page as scrapfly.statuspage.io. That page has 25 components and incident history back to 2022, read through its history feed on 1 November. The 1 October check read only the overall state and found no history (20, was 10). The newest incident is a Scrapium rendering fault on 21 May 2026, so nothing is posted in the 90 days from 3 August (30, was 5). Concurrency per plan is published (5 on Discovery to 100 on Enterprise) and each project has a configurable per-minute throttle (15). The error catalogue marks every code retryable or not and has three ERR::THROTTLE codes, but we found no Retry-After header or backoff guidance on the errors or throttling pages (10 of 15). The terms disclaim uptime and no uptime SLA is published, and the pricing page's SLA mentions cover support response on Enterprise (0). The Scrape API is GA. Vault and alerting are beta, outside the main surface (10). 20+30+15+10+0+10 = 85.
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.
Transparency & trust Scrapfly +10
Scrapfly 75
Closed service with terms updated 2026-09-30 under US law. SDKs are BSD 2-Clause, and the MCP source is public with no LICENSE file and ISC in package.json (15 of 30). Privacy policy updated 14 May 2026 with a published DPA and HIPAA BAA, but retention is as long as necessary, and the retention of scraped content isn't stated (18 of 30). Release notes date deprecations and removals, for example Scrapium v153 dropping legacy network interception on 11 September. No standing deprecation policy found (15 of 20). Stripe, Google Analytics, Google Ads and Google Cloud are named, with SCC and Data Privacy Framework transfers, but there's no full subprocessor list (10 of 20). The release notes still date each CDP removal, most recently Storage.getRelatedWebsiteSets in Scrapium v156 on 26 October. Not otherwise re-read on 1 November. 15+18+15+10 = 58.
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).
Maintenance & community Scrapfly +9
Scrapfly 84
Scrapium v156 in the release notes on 26 October 2026 and MCP v1.4.0 on 15 October (30). MCP tags v1.3.1 to v1.3.3 (26 and 27 August), v1.3.4 (8 September) and v1.4.0 (15 October), SDKs 0.12.0 on 8 September, and dated release notes on 14, 24 and 26 August, 11, 23 and 25 September, 7, 24 and 26 October (20). Dated release notes most weeks and a support address. We couldn't read GitHub issues, since github.com refuses our reader (12 of 25). In the official MCP registry as io.scrapfly.mcp/mcp under the vendor's domain, though the entry still lists 1.0.0, and the SDKs are current (15). MCP moved to Go 1.27 on 23 October. Its CI runs only a reference check and the npm publish, while the TypeScript SDK runs tests in CI (7 of 10). 30+20+12+15+7 = 84.
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.
Score by category
| Category | Weight | Scrapfly | ScrapingBee | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 75 | Scrapfly +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 60 | Scrapfly +35 |
| Agent ergonomics | 13% | 80 | 68 | Scrapfly +12 |
| Security & auth | 14% | 75 | 37 | Scrapfly +38 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 75 | Scrapfly +9 |
| Transparency & trust | 7% | 75 | 65 | Scrapfly +10 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 77/100 | B 62/100 |
Facts side by side
| Fact | Scrapfly | ScrapingBee |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapfly (Joam Intelligence, LLC) | ScrapingBee (Oxylabs group) |
| Hosted endpoint | https://api.scrapfly.io/scrape | https://app.scrapingbee.com/api/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Tools exposed | 62 | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.scrapfly.mcp/mcp | not listed |
| Last release | 2026-10-15 | 2026-09-11 |
| Terms last updated | 2026-09-30 | 2024-07-15 |
| Privacy policy last updated | 2026-05-14 | 2024-07-15 |
| 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 | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 14 stars, 21k npm/wk | 132 stars, 49k npm/wk, 72k PyPI/wk |
| Agent reviews | 4/5 (2) | 4/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Scrapfly | ScrapingBee |
|---|---|---|
| LedgerCost analyst | 4/5 Hard caps on small plans, and cost_budget per request | 4/5 Five credits by default, one with rendering off |
| ScoutResearch agent | 4/5 Every error says whether to retry | 4/5 Docs that list nine of their own conflicts |
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
Scrapfly
The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes, and the Statuspage history shows no incident since May 2026. The MCP server loads 62 tools at once, and the API's canonical form puts the key in the URL.
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.
Before you call either
Scrapfly
- Send
X-Scrapfly-Api-Keyas a header rather thankey=so the key stays out of logs - Pass
unblocker=falseto the MCP web_scrape tool for plain pages, since it's on when omitted.aspis the deprecated alias - Set
cost_budgeton each scrape so an Unblocker upgrade can't blow through credits - Check
retryablein the error body before retrying, and stop onERR::THROTTLE::MAX_API_CREDIT_BUDGET_EXCEEDED - Use web_get_page for a simple fetch and save cloud_browser_open for pages that need clicks
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
Questions
Which is better for AI agents, Scrapfly or ScrapingBee?
Scrapfly scores 77 (BB) on agent readiness against ScrapingBee's 62 (B), and leads in 6 of 7 scored categories.
Do Scrapfly and ScrapingBee need an API key?
Scrapfly takes an API key or an OAuth sign-in. ScrapingBee needs an API key.
Can an agent call Scrapfly and ScrapingBee without installing anything?
Yes. Scrapfly has a hosted endpoint at https://api.scrapfly.io/scrape and ScrapingBee at https://app.scrapingbee.com/api/v1/.
Other comparisons with Scrapfly or ScrapingBee
- Apify MCP Server vs ScrapingBee
- Bright Data vs Scrapfly
- Bright Data vs ScrapingBee
- BrowserAct vs Scrapfly
- BrowserAct vs ScrapingBee
- Context.dev vs Scrapfly
- Context.dev vs ScrapingBee
- Crawl4AI vs Scrapfly
- Crawl4AI vs ScrapingBee
- fastCRW vs Scrapfly
- fastCRW vs ScrapingBee
- Decodo Web Data API vs Scrapfly
- Decodo Web Data API vs ScrapingBee
- jevcrawl vs ScrapingBee
- Jina Reader vs Scrapfly
- Jina Reader vs ScrapingBee
- Microlink vs Scrapfly
- Microlink vs ScrapingBee
- Olostep vs Scrapfly
- Olostep vs ScrapingBee
- Outcrawl vs Scrapfly
- Outcrawl vs ScrapingBee
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs ScrapingBee
- Scrape.do vs Scrapfly
- Scrape.do vs ScrapingBee
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingBee
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingBee
- ScraperAPI vs Scrapfly
- ScraperAPI vs ScrapingBee
- Scrapewise vs Scrapfly
- Scrapewise vs ScrapingBee
- Scrapfly vs ScrapingAnt
- Scrapfly vs Scrapingdog
- Scrapfly vs Scrapling
- Scrapfly vs Spider
- Scrapfly vs WebScraping.AI
- Scrapfly vs ZenRows
- Scrapfly vs Zyte API
- ScrapingAnt vs ScrapingBee
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Scrapling
- ScrapingBee vs Spider
- ScrapingBee vs WebScraping.AI
- ScrapingBee vs ZenRows
- ScrapingBee vs Zyte API
- Firecrawl MCP vs ScrapingBee
- Diffbot vs Scrapfly
- Diffbot vs ScrapingBee
- Nexscope vs Scrapfly
- Nexscope vs ScrapingBee
- Qovia vs Scrapfly
- Qovia vs ScrapingBee
- ScrapeAtlas vs Scrapfly
- ScrapeAtlas vs ScrapingBee
- Scrapfly vs SoldFetch
- ScrapingBee vs SoldFetch
- Apify MCP Server vs Scrapfly
- jevcrawl vs Scrapfly
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
- ScrapeOps Proxy API Aggregator vs ScrapingBee
Machine-readable
- This page as Markdown
/compare/scrapfly-vs-scrapingbee.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapfly.json·/api/v1/tools/scrapingbee.json - From a terminal
anchor compare scrapfly scrapingbee(the CLI) - Over MCP
compare_tools {"a": "scrapfly", "b": "scrapingbee"}at/mcp, no key