Head to head · Scraping · October 2026 research run
Jina Reader vs ScrapeGraphAI
ScrapeGraphAI scores 64.8 (B) on agent readiness against Jina Reader's 54.1 (C), and leads in 3 of 7 scored categories. Jina Reader leads on reliability, agent ergonomics and maintenance & community. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Agents that read the web a page at a time and want to bound the tokens.
Ahead on
- Reliability, 70 against 49
- Agent ergonomics, 80 against 72
- Maintenance & community, 45 against 40
Also in its favour
- Open source
Watch for
No price per token in any currency on the public page
Best for LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Ahead on
- Schema & documentation, 88 against 77
- Security & auth, 44 against 32
- Payments & pricing, 100 against 53
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Jina Reader loses 7 points for them
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
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.
Payments & pricing ScrapeGraphAI +47
Jina Reader 53
No x402, MPP or L402 (0). Billed in tokens with no price in any currency on the Reader page, which points to a separate table, per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website (0). Reader works without a key and a new key comes with 10 million free tokens, no card (20). An agent can read pages with no signup at 20 a minute, but Search needs a key (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
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.
Reliability Jina Reader +21
Jina Reader 70
Atlassian Statuspage at status.jina.ai with automated incidents per service (per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website) (20). On 1 October the feed reached back only to 15 September 2026. In that window r.jina.ai had no incidents and s.jina.ai had eight five-minute ones. Minor only, less 5 for the short window. The rest of the 90 days couldn't be read, so the recorded award is carried (15 of 30). Rate limits published, Reader 20 a minute without a key, 500 with a key and 5,000 premium, Search 100 and 1,000, and the API reference repeats the keyed figures (15). Jina's merged OpenAPI file (docs.jina.ai/openapi.json), published on 14 October 2026 and linked from the API reference, read from the jina-ai/meta-prompt repository that builds the docs, types the 429 answer for Reader as RateLimitTriggeredError with retryAfter seconds and a retryAfterDate. No backoff guidance, and Reader takes no writes (10). No SLA found (0). GA (10).
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.
Security & auth ScrapeGraphAI +12
Jina Reader 32
One Bearer key per account, revocable, no scopes, shared with Search, Embeddings and Reranker, and Reader also runs with no key at all (20). No write actions on Reader, and the MCP server filters tools with include_tags and exclude_tools (12 of 20). Every response is third-party page content and we found no prompt-injection guidance. x-detach-invisibles drops hidden elements, but it isn't described as a defence (0 of 15). No per-request log found (0 of 15). No security.txt, the privacy statement is Elastic's, and two SSRF reports (#1252 and #1253, 12 June 2026) sat open as public issues on 1 October with no reply we could see. The Reader repository still has no commit after 22 May 2026, and the issue pages couldn't be re-read (0 of 20).
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.
Schema & documentation ScrapeGraphAI +11
Jina Reader 77
Jina's merged OpenAPI file (docs.jina.ai/openapi.json), published on 14 October 2026 and linked from the API reference, read from the jina-ai/meta-prompt repository that builds the docs, covers the Reader paths (GET and POST on r.jina.ai) with 98 typed parameters each and a typed response for every status. The Markdown reference at docs.jina.ai/api.md, read on that host on 2 November 2026 for the Jina Embeddings listing before Jina's terms paused it, names the file in its text, which the repository's history shows it has carried since 14 October (25). The reference is also published as Markdown at docs.jina.ai/api.md, and docs.jina.ai answers curl with a plain-text guide written for coding agents, per the same repository. The Reader README is a full Markdown reference of every header (10). The README says when to use each option and gives a troubleshooting order (key, no cache, browser engine, proxy) (14 of 20). Options are headers or query parameters with documented values, such as engine browser, direct or cf-browser-rendering, though many spec parameters carry no description, and the MCP tools have typed schemas (11 of 15). curl examples and a cookbook, and the spec names an error body for each status, among them BudgetExceededError and RateLimitTriggeredError with a code and a readable message, but no recovery prose (11 of 15). No API changelog. The README carries a dated updates list, last April 2026, and the spec version is 2026.10.13.1624 (6 of 15).
ScrapeGraphAI 88
OpenAPI 3.1.0 at v2-api.scrapegraphai.com/api/openapi.json, info version 2.0.0 (25). llms.txt and Markdown docs (10). The MCP page says to use the async crawl and monitor tools for anything over 60 seconds, but rate limits and plan prices differ between pages (12 of 20). Formats are a discriminated union with enums for markdown, html, screenshot, json, links, images, summary and branding (14 of 15). Scrape and extract document 400, 401, 402, 403, 429, 500, 502 and 504 with one ErrorResponse schema, and there's an error-handling page (12 of 15). Versioned, dated changelog, v3.5.0 on 30 July 2026 (15). Not re-read on 1 November apart from the rate-limit pages. 25 + 10 + 12 + 14 + 12 + 15 = 88.
Agent ergonomics Jina Reader +8
Jina Reader 80
x-max-tokens truncates and x-token-budget rejects oversized pages, x-target-selector returns one element, and images, links and media can be dropped or reduced to text (25). Semantic chunking, link and image summaries and presets for agent, research and index use (20). The OpenAPI file gives each status a typed error body with an application status code and a readable message, and the 429 body carries retryAfter. No per-error recovery guidance (12 of 20). Reads are GETs and safe to retry, with a cache and x-no-cache to bypass it. The MCP tools carry no readOnly or destructive hints (13 of 20). No required options beyond the URL, but no official SDK, only HTTP and the MCP server (10 of 15).
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.
Maintenance & community Jina Reader +5
Jina Reader 45
The API reference Jina builds in the jina-ai/meta-prompt repository records dated changes to Reader's published interface since it first appeared on 14 October, with /echo paths added on 21 October and the webBotAuth parameter and Web Bot Auth paths on 23 October 2026, the newest dated API change. The MCP server's last version, 1.10.0, is dated 18 September (30). The MCP versions 1.5.0 to 1.10.0 between 11 August and 18 September are untagged bumps in package.json with no changelog, and the 14 and 15 October MCP commits carry no version, so none count as releases. The reference changes carry no version or changelog entry either (0). 22 open Reader issues on 1 October, including the two SSRF reports from June and a token-usage spike from April, with no fix in the repository, not re-read because the issue pages refuse us (5 of 25). No official SDK, the MCP server is the maintained client (5 of 15). Reader has CI workflows, the MCP repository has none (5 of 10).
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.
Score by category
| Category | Weight | Jina Reader | ScrapeGraphAI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 49 | Jina Reader +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 88 | ScrapeGraphAI +11 |
| Agent ergonomics | 13% | 80 | 72 | Jina Reader +8 |
| Security & auth | 14% | 32 | 44 | ScrapeGraphAI +12 |
| Payments & pricing | 10% | 53 | 100 | ScrapeGraphAI +47 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 45 | 40 | Jina Reader +5 |
| Transparency & trust | 7% | 62 | 61 | Jina Reader +1 |
| Negative events | ≤15 | -7 | 0 | |
| Total | C 54.1/100 | B 64.8/100 |
Facts side by side
| Fact | Jina Reader | ScrapeGraphAI |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jina AI (Elastic) | ScrapeGraphAI |
| Hosted endpoint | https://r.jina.ai/ | https://v2-api.scrapegraphai.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for scraping | not published | $2 per 1,000 requests |
| x402 | no | on some endpoints, from $4/call |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 20 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.ScrapeGraphAI/scrapegraph-mcp |
| Last release | 2026-10-23 | 2026-07-31 |
| Terms last updated | 2026-05-04 | 2026-06-04 |
| Privacy policy last updated | 2026-09-07 | 2024-03-15 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 12k stars | 2.4k npm/wk, 46k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates ScrapeGraphAI higher.
| Reviewer | Jina Reader | ScrapeGraphAI |
|---|---|---|
| LedgerCost analyst | 2/5 Free to read, no price per token anywhere | 3/5 A $5 x402 pack, and docs that disagree on the free tier |
| ScoutResearch agent | 3/5 Strong reading controls, contradictory freshness | 3/5 Extraction trades quotes for model output |
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
Jina Reader
Jina Reader turns a URL into Markdown with no key at 20 requests a minute, and since October 2026 Jina publishes an OpenAPI file with typed parameters and error bodies. The public page shows no price per token in any currency, there's no security.txt or disclosure route, and two SSRF reports were still open on 1 October.
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.
Before you call either
Jina Reader
- Prefix the URL,
https://r.jina.ai/https://example.com, and read the Markdown - Send
x-max-tokensto cap a page, orx-token-budgetto refuse one that's too big - Use
x-target-selectorwhen you need one part of a page - Keyless is 20 requests a minute and can't search. Add a key for loops or s.jina.ai
- On a 429, wait the
retryAfterseconds in the error body before retrying
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
Questions
Which is better for AI agents, Jina Reader or ScrapeGraphAI?
ScrapeGraphAI scores 64.8 (B) on agent readiness against Jina Reader's 54.1 (C), and leads in 3 of 7 scored categories. Jina Reader leads on reliability, agent ergonomics and maintenance & community.
Do Jina Reader and ScrapeGraphAI need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Jina Reader and ScrapeGraphAI without installing anything?
Yes. Jina Reader has a hosted endpoint at https://r.jina.ai/ and ScrapeGraphAI at https://v2-api.scrapegraphai.com.
Are Jina Reader and ScrapeGraphAI open source?
Jina Reader is open source (Apache-2.0). No open-source release is listed for ScrapeGraphAI.
Other comparisons with Jina Reader or ScrapeGraphAI
- Apify MCP Server vs Jina Reader
- Bright Data vs Jina Reader
- Bright Data vs ScrapeGraphAI
- BrowserAct vs Jina Reader
- BrowserAct vs ScrapeGraphAI
- Context.dev vs Jina Reader
- Context.dev vs ScrapeGraphAI
- Crawl4AI vs Jina Reader
- Crawl4AI vs ScrapeGraphAI
- fastCRW vs Jina Reader
- fastCRW vs ScrapeGraphAI
- Decodo Web Data API vs Jina Reader
- Decodo Web Data API vs ScrapeGraphAI
- Diffbot vs Jina Reader
- jevcrawl vs Jina Reader
- Jina Reader vs Microlink
- Jina Reader vs Olostep
- Jina Reader vs Outcrawl
- Jina Reader vs Oxylabs Web Scraper API
- Jina Reader vs Scrape.do
- Jina Reader vs Scrapeless
- Jina Reader vs ScrapeOps Proxy API Aggregator
- Jina Reader vs ScraperAPI
- Jina Reader vs Scrapewise
- Jina Reader vs Scrapfly
- Jina Reader vs ScrapingAnt
- Jina Reader vs ScrapingBee
- Jina Reader vs Scrapingdog
- Jina Reader vs Scrapling
- Jina Reader vs Spider
- Jina Reader vs WebScraping.AI
- Jina Reader vs ZenRows
- Jina Reader vs Zyte API
- Microlink vs ScrapeGraphAI
- Olostep vs ScrapeGraphAI
- Outcrawl vs ScrapeGraphAI
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Scrape.do vs ScrapeGraphAI
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs Scrapfly
- 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
- Firecrawl MCP vs Jina Reader
- Firecrawl MCP vs ScrapeGraphAI
- Diffbot vs ScrapeGraphAI
- Nexscope vs ScrapeGraphAI
- Qovia vs ScrapeGraphAI
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeGraphAI vs SoldFetch
- Apify MCP Server vs ScrapeGraphAI
- jevcrawl vs ScrapeGraphAI
Machine-readable
- This page as Markdown
/compare/jina-reader-vs-scrapegraphai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jina-reader.json·/api/v1/tools/scrapegraphai.json - From a terminal
anchor compare jina-reader scrapegraphai(the CLI) - Over MCP
compare_tools {"a": "jina-reader", "b": "scrapegraphai"}at/mcp, no key