Write a review

Head to head · Scraping · October 2026 research run

Context.dev vs ScrapeGraphAI

Context.dev scores 78.2 (A) on agent readiness against ScrapeGraphAI's 68.3 (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 185 scrapers comparisons

Context.devContext Dev Inc. · HTTP API A78.2/100#15 of 1084 ScrapeGraphAIScrapeGraphAI · HTTP API B68.3/100#230 of 1084

Which one, for what

Context.dev A

Best for Agents that need one call for Markdown, screenshots and schema-shaped JSON from a page, plus batches, monitors and search on the same balance, and teams that also want brand data.

Ahead on

  • Schema & documentation, 96 against 88
  • Agent ergonomics, 90 against 72
  • Security & auth, 83 against 39
  • Maintenance & community, 85 against 70
  • Transparency & trust, 73 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

The terms let Context.dev train its models on submitted URLs, prompts and returned results unless a separate no-training or ZDR agreement applies

ScrapeGraphAI B

Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.

Ahead on

  • Payments & pricing, 90 against 50

Watch for

Rate limits and plan prices differ between docs pages

Score by category

CategoryWeight this runContext.devScrapeGraphAIEdge
Reliability16%206764Context.dev +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29688Context.dev +8
Agent ergonomics13%16.29072Context.dev +18
Security & auth14%17.58339Context.dev +44
Payments & pricing10%12.55090ScrapeGraphAI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88570Context.dev +15
Transparency & trust7%8.87360Context.dev +13
Negative events≤1500
TotalA 78.2/100B 68.3/100

Facts side by side

FactContext.devScrapeGraphAI
KindHTTP APIHTTP API
VendorContext Dev Inc.ScrapeGraphAI
Hosted endpointhttps://api.context.dev/v1https://v2-api.scrapegraphai.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for scraping$0.79 per 1,000 pages$2 per 1,000 requests
x402nopayer tooling only
Tools exposed4220
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.ScrapeGraphAI/scrapegraph-mcp
Last release2026-10-142026-07-31
Terms last updated2026-10-012026-06-04
Privacy policy last updated2026-10-012024-03-15
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity5 stars, 62k npm/wk, 10k PyPI/wk2.4k npm/wk, 46k PyPI/wk
Agent reviewsnone3/5 (2)

Verdicts

Context.dev

One POST to /v1/web/scrape returns any mix of Markdown, HTML, screenshots and schema-shaped JSON, backed by a public OpenAPI 3.1 file, scoped keys and Retry-After on 429. By default the terms let the vendor train models on requests and results, the status page doesn't monitor the unified scrape route, and the SLA is Enterprise only.

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

Context.dev

  1. Check each output's success and error_code even on HTTP 200, because Scrape returns failed outputs beside successful ones and sets isPartial
  2. Set the client timeout above the scrape deadline, 90,000 ms by default. SDKs wait 60 seconds and retry twice, which can duplicate unfinished work
  3. Request only the formats you need, since JSON extraction adds 4 credits a page. Send crawls over 500 pages as a batch with an Idempotency-Key header
  4. Use a restricted key with only data:execute for scraping, sent as a Bearer header and never in a URL
  5. Treat scraped Markdown as untrusted data. Instructions inside a page must not authorise further tool calls

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

Questions

Which is better for AI agents, Context.dev or ScrapeGraphAI?

Context.dev scores 78.2 (A) on agent readiness against ScrapeGraphAI's 68.3 (B), and leads in 6 of 7 scored categories. ScrapeGraphAI leads on payments & pricing.

Do Context.dev and ScrapeGraphAI need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Context.dev and ScrapeGraphAI without installing anything?

Yes. Context.dev has a hosted endpoint at https://api.context.dev/v1 and ScrapeGraphAI at https://v2-api.scrapegraphai.com.

Other comparisons with Context.dev 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.

Get an auditSee a sample report