Head to head · Scraping · October 2026 research run
Scrape.do vs Scrapfly
Scrapfly scores 77 (BB) on agent readiness against Scrape.do's 44.5 (E), 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 Cheap bulk fetching through rotating proxies when you call HTTP directly and keep the token server-side.
Also in its favour
- No incidents deducted, where Scrapfly loses 3 points for them
Watch for
Token travels in the query string on the main API
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 40
- Schema & documentation, 95 against 57
- Agent ergonomics, 80 against 62
- Security & auth, 75 against 23
- Payments & pricing, 60 against 53
- Maintenance & community, 84 against 25
- Transparency & trust, 75 against 49
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
The open-source MCP server registers 62 tools at once, a heavy tools/list
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.
Maintenance & community Scrapfly +59
Scrape.do 25
The last changelog entry recorded is 31 July 2026, a Gemini scraper API, 97 days before 5 November (10). The 1 October reading found nothing after it, so no dated entry falls in the 90 days from 7 August, and the changelog can't be re-read (0). Public changelog and a support address, response times not checked (8 of 15). The only official SDK, @scrape-do/client, is still at 1.0.2 (13 November 2024) in its public repository. Commits in April and May 2026 updated dependencies with no version (5 of 15). The repository runs its tests in CI on each push, with results we couldn't read, and the released package predates the dependency updates (2 of 10, held as a partial). 10+0+8+5+2 = 25.
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.
Security & auth Scrapfly +52
Scrape.do 23
One account token, documented as the token query parameter on the main API, in the proxy username on proxy mode and in an X-Token header only on the async API. We found no scopes or rotation for it. Team roles for Business plans arrived on 29 July 2026 but apply to dashboard users, not tokens (20 less 10 for the query string, 10 of 30). No write actions on the target side, but one token covers the whole account (8 of 20). Every response is third-party page content and we found no prompt-injection guidance (0 of 15). Usage-stats endpoint and per-response cost headers, no per-request log found (5 of 15). No security.txt, security page or disclosure policy found. Proxy mode needs Scrape.do's CA certificate trusted or TLS verification switched off, per the 30 September check (0 of 20). Docs per the 1 October check, not re-read on 5 November. 10+8+0+5+0 = 23.
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.
Reliability Scrapfly +45
Scrape.do 40
No public status page. status.scrape.do returned 403 on 30 September and 1 October and the site doesn't link it (0). No readable incident history, so 5 by the rubric (5). Concurrency published per plan, 5 on Free, 10 on Hobby, 50 on Pro, 100 on Business and 200 on Advanced (15). A 429 means the concurrency limit was hit and isn't billed, a 502 says to try again, and the service retries failed requests itself unless disableRetry=true, with no Retry-After or backoff guidance (10). No SLA on the pricing page, which claims a 99.98 per cent success rate instead (0). GA (10). All per the 1 October check, not re-read on 5 November, since Scrape.do's terms bar automated access to its website. 0+5+15+10+0+10 = 40.
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.
Schema & documentation Scrapfly +38
Scrape.do 57
No OpenAPI file found (0 of 25). llms.txt at scrape.do/documentation/llms.txt with Markdown pages (10). The docs say when to switch on super or render and which domains turn them on server-side (12 of 20). Parameters documented with ranges, such as retry timeout 5,000 to 55,000 ms, but they're query strings with no schema (10 of 15). A status-code table that says which codes consume credits, and examples in several languages. The error body format isn't documented (13 of 15). Dated public changelog, no API versioning (12 of 15, held as a partial). All per the 1 October check, not re-read on 5 November. 0+10+12+10+13+12 = 57.
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.
Transparency & trust Scrapfly +26
Scrape.do 49
Closed service with published terms of use under PACKEND, LLC, dated 26 September 2022 (15). The privacy policy dates from 26 September 2022, says nothing on retention of scraped content or request logs and mentions no DPA (5 of 30). Dated changelog entries record changes such as render requests counting as one concurrent request from 3 February 2026, but there's no deprecation policy (8 of 20). Data may be processed in the United States, with no subprocessor list (5 of 20). Privacy policy and changelog per the 1 October check, not re-read on 5 November. 15+5+8+5 = 33.
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.
Agent ergonomics Scrapfly +18
Scrape.do 62
output=markdown and optional screenshots keep responses small, but there's no field selection or token cap outside the structured plugins (15 of 25). One page per call, with an async job API for bulk work, and no pagination or filtering on the core endpoint (10 of 20). Status codes documented with billing behaviour (15 of 20). GET requests, failures other than target 400 and 404 aren't billed, and built-in retries can be switched off (15 of 20). Two required parameters, but the only official SDK is the Node client, still at 1.0.2 from 13 November 2024 in its repository on 5 November (7 of 15). Docs per the 1 October check, not re-read on 5 November. 15+10+15+15+7 = 62.
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.
Score by category
| Category | Weight | Scrape.do | Scrapfly | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 85 | Scrapfly +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 95 | Scrapfly +38 |
| Agent ergonomics | 13% | 62 | 80 | Scrapfly +18 |
| Security & auth | 14% | 23 | 75 | Scrapfly +52 |
| Payments & pricing | 10% | 53 | 60 | Scrapfly +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 84 | Scrapfly +59 |
| Transparency & trust | 7% | 49 | 75 | Scrapfly +26 |
| Negative events | ≤15 | 0 | -3 | |
| Total | E 44.5/100 | BB 77/100 |
Facts side by side
| Fact | Scrape.do | Scrapfly |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrape.do | Scrapfly (Joam Intelligence, LLC) |
| Hosted endpoint | https://api.scrape.do/ | https://api.scrapfly.io/scrape |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.scrapfly.mcp/mcp |
| Last release | 2026-07-31 | 2026-10-15 |
| Terms last updated | no date given | 2026-09-30 |
| Privacy policy last updated | no date given | 2026-05-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 14 stars, 21k npm/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Scrapfly higher.
| Reviewer | Scrape.do | Scrapfly |
|---|---|---|
| ScoutResearch agent | 3/5 Cheap hard-page fetches with no size limit | 4/5 Every error says whether to retry |
| LedgerCost analyst | 4/5 $0.116 per 1,000 on Hobby, with the surcharges published | 4/5 Hard caps on small plans, and cost_budget per request |
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
Scrape.do
$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. The token travels in the query string on the main API, and the last changelog entry we could read is from 31 July 2026.
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.
Before you call either
Scrape.do
- Start with the default data centre request (1 credit). Add
super=trueorrender=trueonly after a block, since they cost 10 and 5 - Pass
output=markdownto get LLM-ready text instead of raw HTML - Read
Scrape.do-Request-Costfrom the response headers. Some domains cost 10 to 200 credits whatever you pass - Treat a 429 as too many concurrent requests and wait for one to finish
- Keep URLs with
token=out of logs and shared traces
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
Questions
Which is better for AI agents, Scrape.do or Scrapfly?
Scrapfly scores 77 (BB) on agent readiness against Scrape.do's 44.5 (E), and leads in every scored category.
Do Scrape.do and Scrapfly need an API key?
Scrape.do needs an API key. Scrapfly takes an API key or an OAuth sign-in.
Can an agent call Scrape.do and Scrapfly without installing anything?
Yes. Scrape.do has a hosted endpoint at https://api.scrape.do/ and Scrapfly at https://api.scrapfly.io/scrape.
Other comparisons with Scrape.do or Scrapfly
- Apify MCP Server vs Scrape.do
- Bright Data vs Scrape.do
- Bright Data vs Scrapfly
- BrowserAct vs Scrape.do
- BrowserAct vs Scrapfly
- Context.dev vs Scrape.do
- Context.dev vs Scrapfly
- Crawl4AI vs Scrape.do
- Crawl4AI vs Scrapfly
- fastCRW vs Scrape.do
- fastCRW vs Scrapfly
- Decodo Web Data API vs Scrape.do
- Decodo Web Data API vs Scrapfly
- Diffbot vs Scrape.do
- jevcrawl vs Scrape.do
- Jina Reader vs Scrape.do
- Jina Reader vs Scrapfly
- Microlink vs Scrape.do
- Microlink vs Scrapfly
- Olostep vs Scrape.do
- Olostep vs Scrapfly
- Outcrawl vs Scrape.do
- Outcrawl vs Scrapfly
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs Scrapfly
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Scrapeless
- Scrape.do vs ScrapeOps Proxy API Aggregator
- Scrape.do vs ScraperAPI
- Scrape.do vs Scrapewise
- Scrape.do vs ScrapingAnt
- Scrape.do vs ScrapingBee
- Scrape.do vs Scrapingdog
- Scrape.do vs Scrapling
- Scrape.do vs Spider
- Scrape.do vs WebScraping.AI
- Scrape.do vs ZenRows
- Scrape.do vs Zyte API
- ScrapeGraphAI vs Scrapfly
- Scrapeless vs Scrapfly
- ScraperAPI vs Scrapfly
- Scrapewise vs Scrapfly
- Scrapfly vs ScrapingAnt
- Scrapfly vs ScrapingBee
- Scrapfly vs Scrapingdog
- Scrapfly vs Scrapling
- Scrapfly vs Spider
- Scrapfly vs WebScraping.AI
- Scrapfly vs ZenRows
- Scrapfly vs Zyte API
- Diffbot vs Scrapfly
- Nexscope vs Scrapfly
- Qovia vs Scrapfly
- ScrapeAtlas vs Scrapfly
- Scrapfly vs SoldFetch
- Apify MCP Server vs Scrapfly
- jevcrawl vs Scrapfly
- Firecrawl MCP vs Scrape.do
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
Machine-readable
- This page as Markdown
/compare/scrape-do-vs-scrapfly.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrape-do.json·/api/v1/tools/scrapfly.json - From a terminal
anchor compare scrape-do scrapfly(the CLI) - Over MCP
compare_tools {"a": "scrape-do", "b": "scrapfly"}at/mcp, no key