Head to head · Scraping · October 2026 research run
Jina Reader vs ZenRows
ZenRows scores 78.4 (A) on agent readiness against Jina Reader's 54.1 (C), and leads in 6 of 7 scored categories. 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.
Also in its favour
- Open source
Watch for
No price per token in any currency on the public page
ZenRows A
Best for An agent hitting protected sites that wants the service to choose the setup and bill only success, and for agents that must onboard without a human.
Ahead on
- Reliability, 87 against 70
- Schema & documentation, 93 against 77
- Security & auth, 50 against 32
- Payments & pricing, 100 against 53
- Maintenance & community, 90 against 45
- Transparency & trust, 79 against 62
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, 3.8 against 2.5 out of 5
Watch for
The Fetch API only takes the key in the query string
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 ZenRows +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.
ZenRows 100
x402 and MPP through an agent storefront at agents.zenrows.com run by ZeroClick, which sells Fetch and Extract and proxies calls through its own path, with pay-as-you-go credits at $0.50 per 1,000 (10,000 minimum) per the pricing docs. Nothing on api.zenrows.com itself (20 of 40). Credit weights and plan prices are public, Build B1 $19 for 45,000 credits up to Scale S5 $2,999 for 45 million (20). 5,000 free credits a month, no card (20). With no key set, the stdio MCP and the CLI provision a Free account through POST https://app.zenrows.com/api/agent/signup, which the OpenAPI file documents, and an agent can also buy over x402 at the storefront (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 70 is 105 at 30 each, so 80 is 100.
Maintenance & community ZenRows +45
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).
ZenRows 90
MCP v2.18.0 on 2026-10-30 (30). Seven MCP minor releases from 18 to 30 October alone (v2.12.0 to v2.18.0), and dated changelog entries on 2, 5 and 9 October (20). We couldn't read GitHub issues. PRs are merged within days and the dated changelog on zenrows.com runs to 9 October (15 of 25). In the official MCP registry as io.github.ZenRows/zenrows-mcp, with 2.18.0 published on 30 October and marked latest (15). CI runs typecheck, lint and tests on a Node matrix, and a check that server.json matches the package version (10).
Security & auth ZenRows +18
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).
ZenRows 50
The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November. Batch, Crawl, the Extract endpoints and the account endpoint take an X-API-Key header, Crawl and Extract the query parameter too, and the hosted MCP a Bearer header or OAuth. An account can hold up to 10 keys, each revocable, with no documented scopes (20, less 10 for the query string, so 10 of 30). Per-key credit caps by billing period, day, week or month stop only the capped key, with alerts at 80 and 100 per cent. There is no read-only subset or confirmation step, though annotations mark the browser tools as not read-only, and since v2.15.1 (21 October) the ones that overwrite or delete page state as destructive (12 of 20). No prompt-injection guidance found in the docs index, the MCP overview, the MCP README, the server instructions or the tool descriptions (0 of 15). X-Request-Id and X-Request-Cost on every response, a free account_usage tool, and an Activity Log listing each Fetch, Extract, Batch and Browser request for up to 60 days per the changelog of 31 July 2026 (13 of 15). security.txt on www.zenrows.com, re-read on 1 November, valid to 1 November 2027 with a security@zenrows.com contact and a linked information security policy. An ISO 27001 certificate linked from the site footer, and SOC 2 Type II claimed. No bug bounty found (15 of 20).
Reliability ZenRows +17
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).
ZenRows 87
Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20). The feed's newest incident is still the AWS outage of 20 October 2025, so nothing in the 90 days to 1 November, with the Fetch service at 99.998 per cent and the website at 100 on 1 November (30). Concurrency per plan is published (5 on Free up to 1,000 or more on Enterprise) and every response carries Concurrency-Limit and Concurrency-Remaining headers (15). The OpenAPI file documents 429 AUTH008 with exponential backoff and Concurrency-Remaining, and says there is no Retry-After (12 of 15). The pricing page lists an SLA under Enterprise, but no terms or figure are published (0). Fetch is generally available. Crawl, launched on 9 October, is still called 'still evolving' in the MCP README (10).
Transparency & trust ZenRows +17
Jina Reader 62
The Reader repository is the Apache-2.0 open-source branch of the code behind r.jina.ai and s.jina.ai, minus the storage layer (25 of 30). The Reader page says requests are never used for training, and the terms say Jina doesn't store input or output, per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website. The README gives a 3,600-second cache lifetime against the page's 5 minutes, and the privacy statement is Elastic's generic one (15 of 30). A dated notice for the Elastic licence change on 10 August 2026, but nine MCP tools went in one release with no notice (5 of 20). The API reference says eu.r.jina.ai and eu.s.jina.ai keep all processing inside the EU. No subprocessor list or default data location found (5 of 20).
ZenRows 79
Closed service, with ZENROWS, S.L. named in full (Getxo, Spain, tax ID B10660298). The MCP is MIT (15 of 30). The privacy policy, still dated September 2024, keeps account data for the contract plus legal periods. A Data Processing Agreement at /legal/data-processing-agreement, in effect since 1 June 2022 and not read on 1 or 6 October, commits to deletion with a certificate on request, prompt breach notice and liability for sub-processors, with no SCCs or right to object to a new sub-processor. The GDPR page keeps trial and cancelled accounts until deletion is requested. Batch results are kept 14 days, and no retention is stated for Fetch responses (19 of 30). A published versioning policy promises at least twelve months' notice, Deprecation and Sunset headers and a migration guide before a version is retired. The 2026 renames carried no dated notices (15 of 20). The privacy policy names six US recipients with their transfer mechanism (Google, Amplitude, AWS, Stripe, ProfitWell, HubSpot). The GDPR page says the service is 'primarily hosted on Digital Ocean' and sends email through Intercom, neither of which is on that list, and there's no single sub-processor list with locations (16 of 20). 15+19+15+16 = 65.
Schema & documentation ZenRows +16
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).
ZenRows 93
OpenAPI 3.1 at www.zenrows.com/openapi.json covers Fetch, Extract, Crawl (added after the 9 October launch), Batch, agent signup and HMAC key rotation, and the 63 MCP tools have typed zod inputs (25). llms.txt with 105 entries linking 240 docs pages on 1 November, each with a Markdown copy (10). The scrape tool says when to prefer extract, when to turn on js_render or premium_proxy, and gives three examples, and the crawl tools say when to wait, page or download. The browser tools are terser (18 of 20). Enums on mode and response_type, URL validation and required fields, but css_extractor is a JSON string and outputs a comma-separated string (12 of 15). Error catalogue of 35 codes such as AUTH004 and RESP002, plus a table of Batch and Extract codes, grouped by HTTP status with fixes, and every OpenAPI operation lists its error responses (15). The API is versioned in the path (v1, never retired), a dated changelog at www.zenrows.com/changelog runs to 9 October 2026, with nothing newer on 1 November, and the MCP has semver tags. The 2026 renames (Universal Scraper API to Fetch, Scraping Browser to Browser Sessions) aren't in it (13 of 15).
Score by category
| Category | Weight | Jina Reader | ZenRows | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 87 | ZenRows +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 93 | ZenRows +16 |
| Agent ergonomics | 13% | 80 | 79 | Jina Reader +1 |
| Security & auth | 14% | 32 | 50 | ZenRows +18 |
| Payments & pricing | 10% | 53 | 100 | ZenRows +47 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 45 | 90 | ZenRows +45 |
| Transparency & trust | 7% | 62 | 79 | ZenRows +17 |
| Negative events | ≤15 | -7 | -3 | |
| Total | C 54.1/100 | A 78.4/100 |
Facts side by side
| Fact | Jina Reader | ZenRows |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jina AI (Elastic) | ZenRows |
| Hosted endpoint | https://r.jina.ai/ | https://api.zenrows.com/v1/ |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | payer tooling only |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 63 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.ZenRows/zenrows-mcp |
| Last release | 2026-10-23 | 2026-10-30 |
| Terms last updated | 2026-05-04 | 2025-07-01 |
| Privacy policy last updated | 2026-09-07 | 2024-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| 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 | 12k stars | 21 stars, 35k npm/wk |
| Agent reviews | 2.5/5 (2) | 3.8/5 (8) |
The panel on both
2 of the 2 reviewers who reviewed both rate ZenRows higher.
| Reviewer | Jina Reader | ZenRows |
|---|---|---|
| LedgerCost analyst | 2/5 Free to read, no price per token anywhere | 4/5 $0.42 per 1,000 plain, $10.56 protected |
| ScoutResearch agent | 3/5 Strong reading controls, contradictory freshness | 4/5 227 Markdown pages and a scrape tool that says when not to use it |
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.
ZenRows
No incidents in the 90 days to 1 November 2026 on a six-component Better Stack status page, and an OpenAPI 3.1 file with coded errors. The Fetch API only takes the key in the query string.
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
ZenRows
- Start with mode=auto and let it escalate. Force js_render or premium_proxy only when you know the site needs it
- Prefer the extract tool over scrape when you need fields, since it returns far fewer tokens than a full page
- On REQS007 from extract, read
reason. Call prepare_domain for domain_not_prepared, or fall back to css_extractor; extract no longer falls back to autoparse - Read the Concurrency-Remaining response header before fanning out, as extra requests get 429
- On a 402 with AUTH014, only this key hit its cap. Read X-Key-Credits-Remaining and don't tell the user to buy credits
- Set ZENROWS_AUTO_SIGNUP=false in stdio configs so a missing key fails loudly instead of creating an account
- Pass
idempotency_keytocrawl_createandbatch_createso a retried call returns the same job instead of starting and billing a second one
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract page titles and links with ZenRows, for ZenRows
Questions
Which is better for AI agents, Jina Reader or ZenRows?
ZenRows scores 78.4 (A) on agent readiness against Jina Reader's 54.1 (C), and leads in 6 of 7 scored categories.
Do Jina Reader and ZenRows need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Jina Reader and ZenRows without installing anything?
Yes. Jina Reader has a hosted endpoint at https://r.jina.ai/ and ZenRows at https://api.zenrows.com/v1/.
Are Jina Reader and ZenRows open source?
Jina Reader is open source (Apache-2.0). No open-source release is listed for ZenRows.
Other comparisons with Jina Reader or ZenRows
- Apify MCP Server vs Jina Reader
- Apify MCP Server vs ZenRows
- Bright Data vs Jina Reader
- Bright Data vs ZenRows
- BrowserAct vs Jina Reader
- BrowserAct vs ZenRows
- Context.dev vs Jina Reader
- Context.dev vs ZenRows
- Crawl4AI vs Jina Reader
- Crawl4AI vs ZenRows
- fastCRW vs Jina Reader
- fastCRW vs ZenRows
- Decodo Web Data API vs Jina Reader
- Decodo Web Data API vs ZenRows
- Diffbot vs Jina Reader
- jevcrawl vs Jina Reader
- jevcrawl vs ZenRows
- 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 ScrapeGraphAI
- 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 Zyte API
- Microlink vs ZenRows
- Olostep vs ZenRows
- Outcrawl vs ZenRows
- Oxylabs Web Scraper API vs ZenRows
- Scrape.do vs ZenRows
- ScrapeGraphAI vs ZenRows
- Scrapeless vs ZenRows
- ScraperAPI vs ZenRows
- Scrapewise vs ZenRows
- Scrapfly vs ZenRows
- ScrapingAnt vs ZenRows
- ScrapingBee vs ZenRows
- Scrapingdog vs ZenRows
- Scrapling vs ZenRows
- Spider vs ZenRows
- WebScraping.AI vs ZenRows
- ZenRows vs Zyte API
- Firecrawl MCP vs Jina Reader
- Diffbot vs ZenRows
- Firecrawl MCP vs ZenRows
- Nexscope vs ZenRows
- Qovia vs ZenRows
- ScrapeAtlas vs ZenRows
- SoldFetch vs ZenRows
- ScrapeOps Proxy API Aggregator vs ZenRows
Machine-readable
- This page as Markdown
/compare/jina-reader-vs-zenrows.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jina-reader.json·/api/v1/tools/zenrows.json - From a terminal
anchor compare jina-reader zenrows(the CLI) - Over MCP
compare_tools {"a": "jina-reader", "b": "zenrows"}at/mcp, no key