Head to head · Scraping · October 2026 research run

Scrape.do vs ScrapeGraphAI

ScrapeGraphAI has a score of 68.3 (B) against Scrape.do's 44 (E). Both do scraping. The largest gap is payments & pricing, 55 points.

Which one, for what

Pick Scrape.do for

No category where it leads by five points or more.

Pick ScrapeGraphAI for

  • reliability (+24)
  • schema & documentation (+31)
  • agent ergonomics (+10)
  • security & auth (+16)
  • payments & pricing (+55)
  • maintenance & community (+25)
  • transparency & trust (+12)

Score by category

CategoryWeight this runScrape.doScrapeGraphAIEdge
Reliability16%204064ScrapeGraphAI +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25788ScrapeGraphAI +31
Agent ergonomics13%16.26272ScrapeGraphAI +10
Security & auth14%17.52339ScrapeGraphAI +16
Payments & pricing10%12.53590ScrapeGraphAI +55
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84570ScrapeGraphAI +25
Transparency & trust7%8.84961ScrapeGraphAI +12
Negative events≤1500
Total44 · E68.3 · B

Facts side by side

FactScrape.doScrapeGraphAI
KindHTTP APIHTTP API
VendorScrape.doScrapeGraphAI
Hosted endpointhttps://api.scrape.do/https://v2-api.scrapegraphai.com
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nopayer tooling only
Licencenonenone
Tools exposednone20
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.ScrapeGraphAI/scrapegraph-mcp
Last release2026-07-312026-07-31
Popularity2 npm/wk2.4k npm/wk, 46k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

Verdicts

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

ScrapeGraphAI

An agent can mint an account and key over x402 or MPP with no signup. Rate limits and plan prices differ between docs pages.

Before you call either

Scrape.do

  1. Start with the default data centre request (1 credit). Add super=true or render=true only after a block, since they cost 10 and 5
  2. Pass output=markdown to get LLM-ready text instead of raw HTML
  3. Read Scrape.do-Request-Cost from the response headers. Some domains cost 10 to 200 credits whatever you pass
  4. Treat a 429 as too many concurrent requests and wait for one to finish
  5. Keep URLs with token= out of logs and shared traces

ScrapeGraphAI

  1. Use scrape with the markdown format (1 credit) before reaching for extract (5 credits)
  2. Read GET https://v2-api.scrapegraphai.com/api/agent/protocols for current packs and prices before paying over x402
  3. MCP tool calls stop at 60 seconds. Use crawl_start and poll for anything longer
  4. Back off 1, 2 then 4 seconds on a 429 rate_limit_exceeded. No Retry-After is sent
  5. Use Orthogonal's x402 gateway when you need to pay per call without a key

Other comparisons with Scrape.do or ScrapeGraphAI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.