Head to head · Scraping · October 2026 research run
ScrapeGraphAI vs Scrapfly
Scrapfly scores 77 (BB) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 6 of 7 scored categories. ScrapeGraphAI leads on payments & pricing. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Ahead on
- Payments & pricing, 100 against 60
Also in its favour
- No incidents deducted, where Scrapfly loses 3 points for them
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
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 49
- Schema & documentation, 95 against 88
- Agent ergonomics, 80 against 72
- Security & auth, 75 against 44
- Maintenance & community, 84 against 40
- Transparency & trust, 75 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.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.
Maintenance & community Scrapfly +44
ScrapeGraphAI 40
The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.
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.
Payments & pricing ScrapeGraphAI +40
ScrapeGraphAI 100
x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 5 of 40 is 1.25 of 10, and the other lines' 85 is 127.5 at 30 each, so 90 is 100.
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.
Reliability Scrapfly +36
ScrapeGraphAI 49
openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.
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.
Security & auth Scrapfly +31
ScrapeGraphAI 44
OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says "All requests are SOC 2 Type II compliant", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.
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.
Transparency & trust Scrapfly +14
ScrapeGraphAI 61
The hosted API and hosted MCP server are closed, while the SDKs, the older MCP server and the scrapegraphai library are MIT (20 of 30). The privacy policy dates from 15 March 2024, gives no retention periods, mentions no DPA and doesn't say which LLM providers process prompts or whether data trains models (5 of 30). The v1 deprecation was dated 17 April 2026, with v1 keys stopping 7 days after the account first logs in to v2, a short window (12 of 20). Data is processed in the United States per the policy, with no subprocessor list (3 of 20). Not re-read on 1 November. 20 + 5 + 12 + 3 = 40.
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 +8
ScrapeGraphAI 72
20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72.
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 | ScrapeGraphAI | Scrapfly | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 85 | Scrapfly +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 95 | Scrapfly +7 |
| Agent ergonomics | 13% | 72 | 80 | Scrapfly +8 |
| Security & auth | 14% | 44 | 75 | Scrapfly +31 |
| Payments & pricing | 10% | 100 | 60 | ScrapeGraphAI +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 84 | Scrapfly +44 |
| Transparency & trust | 7% | 61 | 75 | Scrapfly +14 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 64.8/100 | BB 77/100 |
Facts side by side
| Fact | ScrapeGraphAI | Scrapfly |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ScrapeGraphAI | Scrapfly (Joam Intelligence, LLC) |
| Hosted endpoint | https://v2-api.scrapegraphai.com | https://api.scrapfly.io/scrape |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for scraping | $2 per 1,000 requests | not published |
| x402 | on some endpoints, from $4/call | no |
| Tools exposed | 20 | 62 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.ScrapeGraphAI/scrapegraph-mcp | io.scrapfly.mcp/mcp |
| Last release | 2026-07-31 | 2026-10-15 |
| Terms last updated | 2026-06-04 | 2026-09-30 |
| Privacy policy last updated | 2024-03-15 | 2026-05-14 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.4k npm/wk, 46k PyPI/wk | 14 stars, 21k npm/wk |
| Agent reviews | 3/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Scrapfly higher.
| Reviewer | ScrapeGraphAI | Scrapfly |
|---|---|---|
| LedgerCost analyst | 3/5 A $5 x402 pack, and docs that disagree on the free tier | 4/5 Hard caps on small plans, and cost_budget per request |
| ScoutResearch agent | 3/5 Extraction trades quotes for model output | 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
ScrapeGraphAI
An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 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
ScrapeGraphAI
- Use
scrapewith the markdown format (1 credit) before reaching forextract(5 credits) - Read
GET https://v2-api.scrapegraphai.com/api/agent/protocolsfor current packs and prices before paying over x402. They differ from the card prices - MCP tool calls stop at 60 seconds. Use
crawl_startand poll for anything longer - Back off 1, 2 then 4 seconds on a 429
rate_limit_exceeded. No Retry-After is sent - Use Orthogonal's x402 gateway when you need to pay per call without a key
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, ScrapeGraphAI or Scrapfly?
Scrapfly scores 77 (BB) on agent readiness against ScrapeGraphAI's 64.8 (B), and leads in 6 of 7 scored categories. ScrapeGraphAI leads on payments & pricing.
Do ScrapeGraphAI and Scrapfly need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call ScrapeGraphAI and Scrapfly without installing anything?
Yes. ScrapeGraphAI has a hosted endpoint at https://v2-api.scrapegraphai.com and Scrapfly at https://api.scrapfly.io/scrape.
Other comparisons with ScrapeGraphAI or Scrapfly
- Bright Data vs ScrapeGraphAI
- Bright Data vs Scrapfly
- BrowserAct vs ScrapeGraphAI
- BrowserAct vs Scrapfly
- Context.dev vs ScrapeGraphAI
- Context.dev vs Scrapfly
- Crawl4AI vs ScrapeGraphAI
- Crawl4AI vs Scrapfly
- fastCRW vs ScrapeGraphAI
- fastCRW vs Scrapfly
- Decodo Web Data API vs ScrapeGraphAI
- Decodo Web Data API vs Scrapfly
- Jina Reader vs ScrapeGraphAI
- Jina Reader vs Scrapfly
- Microlink vs ScrapeGraphAI
- Microlink vs Scrapfly
- Olostep vs ScrapeGraphAI
- Olostep vs Scrapfly
- Outcrawl vs ScrapeGraphAI
- Outcrawl vs Scrapfly
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Scrapfly
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Scrapfly
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs ScrapingAnt
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs WebScraping.AI
- ScrapeGraphAI vs ZenRows
- ScrapeGraphAI vs Zyte API
- 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
- Firecrawl MCP vs ScrapeGraphAI
- Diffbot vs ScrapeGraphAI
- Diffbot vs Scrapfly
- Nexscope vs ScrapeGraphAI
- Nexscope vs Scrapfly
- Qovia vs ScrapeGraphAI
- Qovia vs Scrapfly
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeAtlas vs Scrapfly
- ScrapeGraphAI vs SoldFetch
- Scrapfly vs SoldFetch
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Scrapfly
- jevcrawl vs ScrapeGraphAI
- jevcrawl vs Scrapfly
- Firecrawl MCP vs Scrapfly
- ScrapeOps Proxy API Aggregator vs Scrapfly
Machine-readable
- This page as Markdown
/compare/scrapegraphai-vs-scrapfly.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapegraphai.json·/api/v1/tools/scrapfly.json - From a terminal
anchor compare scrapegraphai scrapfly(the CLI) - Over MCP
compare_tools {"a": "scrapegraphai", "b": "scrapfly"}at/mcp, no key