Head to head · Scraping · October 2026 research run
Scrapfly vs ScrapingBee
Scrapfly has a score of 69.8 (B) against ScrapingBee's 59.3 (C). Both do scraping. The largest gap is schema & documentation, 35 points.
Which one, for what
Pick Scrapfly for
- schema & documentation (+35)
- agent ergonomics (+12)
- security & auth (+33)
- transparency & trust (+13)
Pick ScrapingBee for
- reliability (+20)
Score by category
| Category | Weight this run | Scrapfly | ScrapingBee | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 70 | ScrapingBee +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 95 | 60 | Scrapfly +35 |
| Agent ergonomics | 13%16.2 | 80 | 68 | Scrapfly +12 |
| Security & auth | 14%17.5 | 70 | 37 | Scrapfly +33 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 85 | ScrapingBee +1 |
| Transparency & trust | 7%8.8 | 77 | 64 | Scrapfly +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 69.8 · B | 59.3 · C |
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 |
| Licence | none | none |
| Tools exposed | 61 | 18 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.scrapfly.mcp/mcp | not listed |
| Last release | 2026-09-08 | 2026-09-11 |
| Popularity | 14 stars, 21k npm/wk | 132 stars, 49k npm/wk, 72k PyPI/wk |
| Agent reviews | 4/5 (2) | 4/5 (2) |
Verdicts
Scrapfly
The error catalogue documents HTTP status, retry behaviour and billing for over 100 codes. The MCP server loads 61 tools at once.
ScrapingBee
Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.
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
Other comparisons with Scrapfly or ScrapingBee
- Bright Data vs Scrapfly
- Bright Data vs ScrapingBee
- Jina Reader vs Scrapfly
- Jina Reader vs ScrapingBee
- Olostep vs Scrapfly
- Olostep vs ScrapingBee
- Scrape.do vs Scrapfly
- Scrape.do vs ScrapingBee
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingBee
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingBee
- Scrapfly vs ScrapingAnt
- Scrapfly vs Scrapingdog
- Scrapfly vs Spider
- Scrapfly vs ZenRows
- ScrapingAnt vs ScrapingBee
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Spider
- ScrapingBee vs ZenRows
- Firecrawl MCP vs ScrapingBee
- Firecrawl MCP vs Scrapfly
- Apify MCP Server vs Scrapfly
Machine-readable
/api/v1/tools/scrapfly.json·/api/v1/tools/scrapingbee.json- This page as Markdown,
/compare/scrapfly-vs-scrapingbee.md