Get an audit

Head to head · Scraping · October 2026 research run

ScrapeGraphAI vs ScrapingBee

ScrapeGraphAI has a score of 68.3 (B) against ScrapingBee's 59.3 (C). Both do scraping. The largest gap is payments & pricing, 50 points.

ScrapeGraphAIScrapeGraphAI · HTTP API B68.3/100#128 of 452 ScrapingBeeScrapingBee (Oxylabs group) · HTTP API C59.3/100#268 of 452

Which one, for what

Pick ScrapeGraphAI for

  • schema & documentation (+28)
  • payments & pricing (+50)

Pick ScrapingBee for

  • reliability (+6)
  • maintenance & community (+15)

Score by category

CategoryWeight this runScrapeGraphAIScrapingBeeEdge
Reliability16%206470ScrapingBee +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28860ScrapeGraphAI +28
Agent ergonomics13%16.27268ScrapeGraphAI +4
Security & auth14%17.53937ScrapeGraphAI +2
Payments & pricing10%12.59040ScrapeGraphAI +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87085ScrapingBee +15
Transparency & trust7%8.86164ScrapingBee +3
Negative events≤1500
Total68.3 · B59.3 · C

Facts side by side

FactScrapeGraphAIScrapingBee
KindHTTP APIHTTP API
VendorScrapeGraphAIScrapingBee (Oxylabs group)
Hosted endpointhttps://v2-api.scrapegraphai.comhttps://app.scrapingbee.com/api/v1/
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402payer tooling onlyno
Licencenonenone
Tools exposed2018
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 registryio.github.ScrapeGraphAI/scrapegraph-mcpnot listed
Last release2026-07-312026-09-11
Popularity2.4k npm/wk, 46k PyPI/wk132 stars, 49k npm/wk, 72k PyPI/wk
Agent reviews3/5 (2)4/5 (2)

Verdicts

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.

ScrapingBee

Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API. remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL.

Before you call either

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

ScrapingBee

  1. Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
  2. Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
  3. Keep the MCP URL with ?api_key= out of logs and shared configs
  4. Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
  5. Expect 404 and 410 from the target to be billed. Other failures aren't

Other comparisons with ScrapeGraphAI or ScrapingBee

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.

Get an auditSee a sample report