Head to head · Scraping · October 2026 research run
Scrapeless vs Scrapfly
Scrapfly scores 77 (BB) on agent readiness against Scrapeless's 58.1 (C), 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 An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Also in its favour
- No incidents deducted, where Scrapfly loses 3 points for them
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
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 70
- Schema & documentation, 95 against 66
- Agent ergonomics, 80 against 50
- Security & auth, 75 against 37
- Payments & pricing, 60 against 53
- Transparency & trust, 75 against 58
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 4.0 against 2.0 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.
Security & auth Scrapfly +38
Scrapeless 37
One API token per account, sent in the x-api-token header, which the docs say can be replaced and invalidated from the dashboard or through support. No scopes (20). Agent Browser WebSocket connections pass the token as a URL parameter, a documented option, so less 10 (10 of 30). No read-only mode, and the browser tools can click and type on third-party sites without any confirmation step (5 of 20). The MCP README has a security section that calls web data untrusted by default and warns against passing raw scraped content into prompts, with no in-tool mitigation (10 of 15). Browser sessions are recorded, and we found no request log for the other APIs (5 of 15). security.txt is valid (contact system@scrapeless.com, expires 2030), with no disclosure policy or acknowledgement time, and no bug bounty, SOC 2 or ISO 27001 found (7 of 20). 10 + 5 + 10 + 5 + 7 = 37.
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.
Agent ergonomics Scrapfly +30
Scrapeless 50
25 MCP tools, 16 of them browser actions, with no toolsets or read-only subset (15 of 25). crawl_start takes limit and maxDepth, but scrape_markdown and scrape_html take only a URL, with no size or selector control (10 of 20). The MCP returns status_code, a code of rate_limited or api_error, and the upstream message. No API error catalogue found (10 of 20). No readOnlyHint or destructiveHint annotations and no idempotency guidance (0). Most tools need only a URL, and official SDKs exist for Node and Python (15).
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.
Schema & documentation Scrapfly +29
Scrapeless 66
No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 of 15).
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 +17
Scrapeless 58
The MCP server is open source but the LICENSE file says MIT while package.json says ISC. The API is closed, and the terms name NST LABS TECH LTD. with no address or governing law (15 of 30). The privacy policy gives no retention periods beyond tokens kept 24 hours. The Data Processing Agreement (v1.0, effective 7 August 2026, linked from the terms) covers sub-processor notice, SCCs for EEA transfers and deletion on termination, with no retention periods for scraped data (14 of 30). No deprecation policy or dated notices found (0). The DPA's Exhibit 2 names two sub-processors, Airwallex and Intercom, both in the United States, and no hosting location (10 of 20). 15 + 14 + 0 + 10 = 39.
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.
Reliability Scrapfly +15
Scrapeless 70
Better Stack status page at status.scrapeless.com with four groups, Scrapeless API, Scraping Browser, website and dashboard, and residential proxies (20). Every monitor shows 100 per cent uptime over 90 days and the incident list reports none for September, October or November 2026. The list doesn't page back to August, so the earlier clean reading for August is kept (30). No rate-limit numbers found in the docs. The 30 September concurrency figures came from a script-loaded price file and are struck (0). The Results and Polling page documents 429 as rate limit exceeded with reduce-frequency guidance and a one-minute wait for 500s, with no idempotency keys (10). The pricing page names an Enterprise-level SLA but no SLA document is published (0). The APIs are generally available (10). 20 + 30 + 0 + 10 + 0 + 10 = 70.
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.
Payments & pricing Scrapfly +7
Scrapeless 53
No x402, MPP or L402. Crypto top-ups exist but aren't a machine payment protocol (0). The pricing page draws its rate tables by script. The docs publish per-unit rates, Crawl from $1.8 a GB plus $0.09 a browser hour and Web Unlocker from $0.20 per 1,000 URLs, and the Google Search API page gives volume rates below $0.50 per 1,000 on qualifying plans, but no full rate card is readable without script (15 of 20, a partial kept under the in-between rule). The Google Search API page says no credit card is required to start (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Scrapfly 60
No x402, MPP or L402 (0). Credit costs per request type (1 datacentre, 5 with rendering or Unblocker, 25 residential, 60 full-page screenshot) and plan prices are public. Unblocker surcharges per target aren't published, but cost_budget caps them (20). 1,000 free credits, no card, no time limit (20). A person signs up in a browser. OAuth still needs an account (0). Plan prices and the 1,000 free credits with no card re-read on the pricing page on 1 November. 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Score by category
| Category | Weight | Scrapeless | Scrapfly | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 85 | Scrapfly +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 95 | Scrapfly +29 |
| Agent ergonomics | 13% | 50 | 80 | Scrapfly +30 |
| Security & auth | 14% | 37 | 75 | Scrapfly +38 |
| Payments & pricing | 10% | 53 | 60 | Scrapfly +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 84 | Scrapfly +3 |
| Transparency & trust | 7% | 58 | 75 | Scrapfly +17 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 58.1/100 | BB 77/100 |
Facts side by side
| Fact | Scrapeless | Scrapfly |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapeless (NST Labs Tech) | Scrapfly (Joam Intelligence, LLC) |
| Hosted endpoint | https://api.scrapeless.com | https://api.scrapfly.io/scrape |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 25 | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.scrapeless-ai/scrapeless-mcp-server | io.scrapfly.mcp/mcp |
| Last release | 2026-09-16 | 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 | not found in the text | 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 | 169 stars, 423 npm/wk, 216 PyPI/wk | 14 stars, 21k npm/wk |
| Agent reviews | 2/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Scrapfly higher.
| Reviewer | Scrapeless | Scrapfly |
|---|---|---|
| LedgerCost analyst | 2/5 A tenfold price gap between llms.txt and the plan data | 4/5 Hard caps on small plans, and cost_budget per request |
| ScoutResearch agent | 2/5 69,000 characters of tools and a wrong price in llms.txt | 4/5 Every error says whether to retry |
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
Scrapeless
Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package and SDKs in three languages, all released between August and October 2026. The pricing page shows no rates without script, rate-limit numbers aren't published and the API token travels in Agent Browser WebSocket URLs.
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
Scrapeless
- Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
- Call browser_close when done so the session and its billing stop
- Set limit on crawl_start. Unset, it defaults to 10,000 pages
- Poll /result/{taskId} every 1 to 5 seconds after a 201, and back off when a call returns 429
- Fetch AI Scraper results within 5 minutes or set a webhook, since an unfetched result is still billed
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, Scrapeless or Scrapfly?
Scrapfly scores 77 (BB) on agent readiness against Scrapeless's 58.1 (C), and leads in every scored category.
Do Scrapeless and Scrapfly need an API key?
Scrapeless needs an API key. Scrapfly takes an API key or an OAuth sign-in.
Can an agent call Scrapeless and Scrapfly without installing anything?
Yes. Scrapeless has a hosted endpoint at https://api.scrapeless.com and Scrapfly at https://api.scrapfly.io/scrape.
Other comparisons with Scrapeless or Scrapfly
- Bright Data vs Scrapeless
- Bright Data vs Scrapfly
- BrowserAct vs Scrapeless
- BrowserAct vs Scrapfly
- Context.dev vs Scrapeless
- Context.dev vs Scrapfly
- Crawl4AI vs Scrapeless
- Crawl4AI vs Scrapfly
- fastCRW vs Scrapeless
- fastCRW vs Scrapfly
- Decodo Web Data API vs Scrapeless
- Decodo Web Data API vs Scrapfly
- Diffbot vs Scrapeless
- Jina Reader vs Scrapeless
- Jina Reader vs Scrapfly
- Microlink vs Scrapeless
- Microlink vs Scrapfly
- Olostep vs Scrapeless
- Olostep vs Scrapfly
- Outcrawl vs Scrapeless
- Outcrawl vs Scrapfly
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs Scrapfly
- Scrape.do vs Scrapeless
- Scrape.do vs Scrapfly
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs Scrapfly
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- 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
- Firecrawl MCP vs Scrapeless
- Diffbot vs Scrapfly
- Nexscope vs Scrapfly
- Qovia vs Scrapfly
- ScrapeAtlas vs Scrapfly
- Scrapfly vs SoldFetch
- Apify MCP Server vs Scrapeless
- Apify MCP Server vs Scrapfly
- jevcrawl vs Scrapeless
- jevcrawl vs Scrapfly
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
Machine-readable
- This page as Markdown
/compare/scrapeless-vs-scrapfly.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapeless.json·/api/v1/tools/scrapfly.json - From a terminal
anchor compare scrapeless scrapfly(the CLI) - Over MCP
compare_tools {"a": "scrapeless", "b": "scrapfly"}at/mcp, no key