Head to head · Scraping · October 2026 research run
Scrapfly vs Scrapling
Scrapfly scores 77 (BB) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community. 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 65
- Schema & documentation, 95 against 81
- Agent ergonomics, 80 against 71
- Security & auth, 75 against 39
- Transparency & trust, 75 against 52
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
The open-source MCP server registers 62 tools at once, a heavy tools/list
Best for Agents that need to fetch and drive pages locally, including JavaScript-heavy or bot-protected ones, without a hosted scraping bill.
Ahead on
- Payments & pricing, 90 against 60
- Maintenance & community, 93 against 84
Also in its favour
- No key needed to call it
- Open source
- No incidents deducted, where Scrapfly loses 3 points for them
Watch for
Version 0.5.1 with a Beta classifier. v0.4.15, v0.5 and v0.5.1 each carried breaking changes, the last in a patch release
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 +36
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.
Scrapling 39
Read as local software with an optional HTTP transport. stdio needs no credential. Over HTTP the server refuses to start without a token or an explicit --no-auth, and accepts one shared bearer token with no scopes, rotated by restarting (15). Annotations let a client gate the destructive tools, and follow_redirects defaults to safe, which blocks redirects to private addresses. A direct request to localhost or a private address is not refused, and there is no read-only mode (10). Hidden elements, aria-hidden content, zero-width characters, comments and template tags are stripped by default before page text reaches the model, as documented in the MCP guide. The vendor's claim, untested by us (10). Browser sessions record network history the agent and operator can read back. No call log (4). No SECURITY.md, disclosure address or bug bounty in the repository, and GitHub's advisory page couldn't be read (0). 15 + 10 + 10 + 4 + 0 = 39.
Payments & pricing Scrapling +30
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.
Scrapling 90
Free, self-hosted software under BSD-3-Clause with nothing to buy, read with the self-hosted rule. No payment protocol (0), nothing to price (30), free (30), no signup or key (30). 0 + 30 + 30 + 30 = 90.
Transparency & trust Scrapfly +23
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.
Scrapling 52
BSD-3-Clause in LICENSE and the PyPI classifiers (30). No telemetry or usage reporting found in the source. Page traffic goes to the target sites, with optional DNS-over-HTTPS through Cloudflare. There is no privacy statement for the package (15). No deprecation policy. Breaking changes are announced in the release notes with migration guides for v0.5 and the remote-session change (8). Nothing is collected that we could find, but there is no explicit statement on telemetry (12). 30 + 15 + 8 + 12 = 65.
Reliability Scrapfly +20
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.
Scrapling 65
Read on the local-software lines, since the MCP server runs on the user's machine over stdio or a self-run HTTP port. Installs from PyPI (scrapling[ai]) or Docker (pyd4vinci/scrapling, ghcr.io/d4vinci/scrapling), with Python 3.10 or later and 3.10 to 3.13 in the classifiers (20). tests.yml runs tox on Python 3.10 to 3.13 on macOS for pushes and pull requests to main and dev, and the repository holds about 1,390 test functions, 19 test files for the MCP tools among them. Run results on GitHub couldn't be read on 18 November, so passing on main is unchecked (15 of 25). Five issues were open on 18 November 2026 against 104,200 stars, the oldest from 24 October 2025, and two of them had a reply. The v0.5.1 notes credit fixes from outside contributors and close reported issues such as #540 (20 of 25). Breaking changes carry a warning and a migration guide in the changelog, but v0.5.1 broke remote browser connections in a patch release (10 of 15). Version 0.5.1 with a Development Status 4 Beta classifier (0). 20 + 15 + 20 + 10 + 0 = 65.
Schema & documentation Scrapfly +14
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.
Scrapling 81
Read from the server source (scrapling/core/ai/server.py) and docs/ai/mcp-server.md in the repository. Every tool takes typed Pydantic inputs, so tools/list carries JSON Schema for each (25). No llms.txt in the repository, and scrapling.readthedocs.io answers 404 for /llms.txt. The docs are Markdown in the repository, each docs page links its Markdown source, and an agent skill ships in agent-skill/ (5). Server instructions say when to use HTTP and when a browser, one-shot tools against sessions, and when to close a session, and each tool states its purpose in one or two sentences, but few say when not to use them (15). Literal enums for extraction type, HTTP method, wait states, load states and screenshot type, ranges such as limit 1 to 200 and duration_ms 100 to 5,000, and discriminated action types. Proxy and cookie fields take free dictionaries (12). The MCP guide has example prompts and setup for each client. Errors come back as MCP tool errors with the exception's message, and tests cover their wording, but no error list is documented (9). A dated changelog for every release from v0.1 (13 October 2024) to v0.5.1 (4 November 2026), and the server reports its version (15). 25 + 5 + 15 + 12 + 9 + 15 = 81.
Agent ergonomics Scrapfly +9
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.
Scrapling 71
17 tools, and v0.5 and v0.5.1 both shortened the descriptions. No toolsets or read-only subset (15). css_selector narrows fetch output, extraction can be Markdown, HTML, text or an ARIA snapshot with search, main_content_only is on by default, and network history is paged with a cursor and a limit of 1 to 200 (18). Failures from bad input, the browser and curl come back as tool errors with the message, which the v0.5 notes say were made clearer. No error codes an agent can branch on (12). Every tool carries annotations, read-only for fetches and lists and destructive for actions, JavaScript and state files. HTTP requests retry three times by default with a one-second wait (17). Only url is required for a fetch, with schema defaults. One language, Python, plus a CLI and Docker (9). 15 + 18 + 12 + 17 + 9 = 71.
Score by category
| Category | Weight | Scrapfly | Scrapling | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 65 | Scrapfly +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 81 | Scrapfly +14 |
| Agent ergonomics | 13% | 80 | 71 | Scrapfly +9 |
| Security & auth | 14% | 75 | 39 | Scrapfly +36 |
| Payments & pricing | 10% | 60 | 90 | Scrapling +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 93 | Scrapling +9 |
| Transparency & trust | 7% | 75 | 52 | Scrapfly +23 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 77/100 | B 68.5/100 |
Facts side by side
| Fact | Scrapfly | Scrapling |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Scrapfly (Joam Intelligence, LLC) | Karim Shoair |
| Hosted endpoint | https://api.scrapfly.io/scrape | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | stdio, Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | BSD-3-Clause |
| Tools exposed | 62 | 17 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.scrapfly.mcp/mcp | io.github.D4Vinci/Scrapling |
| Last release | 2026-10-15 | 2026-11-04 |
| Terms last updated | 2026-09-30 | no document linked |
| Privacy policy last updated | 2026-05-14 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 14 stars, 21k npm/wk | 104k stars |
| Agent reviews | 4/5 (2) | none |
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.
Scrapling
Scrapling's MCP server gives agents 17 typed tools with read-only and destructive hints, output trimming by CSS selector and default stripping of hidden page text. It is pre-1.0 (0.5.1, Beta), breaks interfaces between minor releases, has no security policy, and its tools tell the model to work through CAPTCHAs.
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
Scrapling
- Start with
make_requestand move tobrowser_fetch_onceonly when the page needs JavaScript or blocks plain HTTP - Pass
css_selectoron fetch tools to cut output. Snapshots need one match or no selector - Read network history with
browser_network_requestsbeforeclose_session, since closing a session drops it - Check the target site's terms and robots.txt yourself. The MCP tools don't read robots.txt, only the spiders do
- If you run the server over HTTP, set
SCRAPLING_MCP_AUTH_TOKENand keep it behind TLS. The token travels in clear over plain HTTP
Questions
Which is better for AI agents, Scrapfly or Scrapling?
Scrapfly scores 77 (BB) on agent readiness against Scrapling's 68.5 (B), and leads in 5 of 7 scored categories. Scrapling leads on payments & pricing and maintenance & community.
Do Scrapfly and Scrapling need an API key?
Scrapfly takes an API key or an OAuth sign-in. Scrapling needs no key.
Can an agent call Scrapfly and Scrapling without installing anything?
Scrapfly has a hosted endpoint at https://api.scrapfly.io/scrape. Scrapling runs on your own machine, with no hosted endpoint listed.
Are Scrapfly and Scrapling open source?
No open-source release is listed for Scrapfly. Scrapling is open source (BSD-3-Clause).
Other comparisons with Scrapfly or Scrapling
- Bright Data vs Scrapfly
- Bright Data vs Scrapling
- BrowserAct vs Scrapfly
- BrowserAct vs Scrapling
- Context.dev vs Scrapfly
- Context.dev vs Scrapling
- Crawl4AI vs Scrapfly
- Crawl4AI vs Scrapling
- fastCRW vs Scrapfly
- fastCRW vs Scrapling
- Decodo Web Data API vs Scrapfly
- Decodo Web Data API vs Scrapling
- Jina Reader vs Scrapfly
- Jina Reader vs Scrapling
- Microlink vs Scrapfly
- Microlink vs Scrapling
- Olostep vs Scrapfly
- Olostep vs Scrapling
- Outcrawl vs Scrapfly
- Outcrawl vs Scrapling
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs Scrapling
- Scrape.do vs Scrapfly
- Scrape.do vs Scrapling
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs Scrapling
- Scrapeless vs Scrapfly
- Scrapeless vs Scrapling
- ScraperAPI vs Scrapfly
- ScraperAPI vs Scrapling
- Scrapewise vs Scrapfly
- Scrapewise vs Scrapling
- Scrapfly vs ScrapingAnt
- Scrapfly vs ScrapingBee
- Scrapfly vs Scrapingdog
- Scrapfly vs Spider
- Scrapfly vs WebScraping.AI
- Scrapfly vs ZenRows
- Scrapfly vs Zyte API
- ScrapingAnt vs Scrapling
- ScrapingBee vs Scrapling
- Scrapingdog vs Scrapling
- Scrapling vs Spider
- Scrapling vs WebScraping.AI
- Scrapling vs ZenRows
- Scrapling vs Zyte API
- Diffbot vs Scrapfly
- Diffbot vs Scrapling
- Firecrawl MCP vs Scrapling
- Nexscope vs Scrapfly
- Nexscope vs Scrapling
- Qovia vs Scrapfly
- Qovia vs Scrapling
- ScrapeAtlas vs Scrapfly
- ScrapeAtlas vs Scrapling
- Scrapfly vs SoldFetch
- Scrapling vs SoldFetch
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Scrapling
- jevcrawl vs Scrapfly
- jevcrawl vs Scrapling
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapling
Machine-readable
- This page as Markdown
/compare/scrapfly-vs-scrapling.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapfly.json·/api/v1/tools/scrapling.json - From a terminal
anchor compare scrapfly scrapling(the CLI) - Over MCP
compare_tools {"a": "scrapfly", "b": "scrapling"}at/mcp, no key