Head to head · Scraping · October 2026 research run
Jina Reader vs Scrapeless
Scrapeless scores 58.1 (C) on agent readiness against Jina Reader's 54.1 (C), and leads in 2 of 7 scored categories. Jina Reader leads on schema & documentation and agent ergonomics. 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
- Schema & documentation, 77 against 66
- Agent ergonomics, 80 against 50
Also in its favour
- Open source
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
Watch for
No price per token in any currency on the public page
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Security & auth, 37 against 32
- Maintenance & community, 81 against 45
Also in its favour
- Runs on your own machine
- Free to start without a card
- No incidents deducted, where Jina Reader loses 7 points for them
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
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.
Maintenance & community Scrapeless +36
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).
Scrapeless 81
The official CLI (scrapeless on npm, its own repository) tagged v0.1.0 on 2026-10-20 (30). In the 90 days from 6 August, MCP server v0.5.0 (20 August), v0.6.0 (28 August), v0.6.1 (2 September) and v0.6.3 (8 September), Node SDK v1.12.0 and v1.12.1, Python SDK v1.3.0 and Go SDK v1.3.0 (16 September) and the CLI (20). GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (one open MCP issue, #10, from 12 August; Discord linked) (12 of 25). Node, Python and Go SDKs are current (15). No CI workflow in the MCP repo; the CLI has one, and the MCP pins @modelcontextprotocol/sdk at ^1.8.0 (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.
Agent ergonomics Jina Reader +30
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).
Scrapeless 50
25 MCP tools, 16 of them browser actions, with no toolsets or read-only subset (15 of 25). crawl_start takes limit and maxDepth, but scrape_markdown and scrape_html take only a URL, with no size or selector control (10 of 20). The MCP returns status_code, a code of rate_limited or api_error, and the upstream message. No API error catalogue found (10 of 20). No readOnlyHint or destructiveHint annotations and no idempotency guidance (0). Most tools need only a URL, and official SDKs exist for Node and Python (15).
Schema & documentation Jina Reader +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).
Scrapeless 66
No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 of 15).
Security & auth Scrapeless +5
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).
Scrapeless 37
One API token per account, sent in the x-api-token header, which the docs say can be replaced and invalidated from the dashboard or through support. No scopes (20). Agent Browser WebSocket connections pass the token as a URL parameter, a documented option, so less 10 (10 of 30). No read-only mode, and the browser tools can click and type on third-party sites without any confirmation step (5 of 20). The MCP README has a security section that calls web data untrusted by default and warns against passing raw scraped content into prompts, with no in-tool mitigation (10 of 15). Browser sessions are recorded, and we found no request log for the other APIs (5 of 15). security.txt is valid (contact system@scrapeless.com, expires 2030), with no disclosure policy or acknowledgement time, and no bug bounty, SOC 2 or ISO 27001 found (7 of 20). 10 + 5 + 10 + 5 + 7 = 37.
Score by category
| Category | Weight | Jina Reader | Scrapeless | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 70 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 66 | Jina Reader +11 |
| Agent ergonomics | 13% | 80 | 50 | Jina Reader +30 |
| Security & auth | 14% | 32 | 37 | Scrapeless +5 |
| Payments & pricing | 10% | 53 | 53 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 45 | 81 | Scrapeless +36 |
| Transparency & trust | 7% | 62 | 58 | Jina Reader +4 |
| Negative events | ≤15 | -7 | 0 | |
| Total | C 54.1/100 | C 58.1/100 |
Facts side by side
| Fact | Jina Reader | Scrapeless |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jina AI (Elastic) | Scrapeless (NST Labs Tech) |
| Hosted endpoint | https://r.jina.ai/ | https://api.scrapeless.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.scrapeless-ai/scrapeless-mcp-server |
| Last release | 2026-10-23 | 2026-09-16 |
| Terms last updated | 2026-05-04 | no date given |
| Privacy policy last updated | 2026-09-07 | no date given |
| 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 | 169 stars, 423 npm/wk, 216 PyPI/wk |
| Agent reviews | 2.5/5 (2) | 2/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Jina Reader higher, the other way from the total score.
| Reviewer | Jina Reader | Scrapeless |
|---|---|---|
| ScoutResearch agent | 3/5 Strong reading controls, contradictory freshness | 2/5 69,000 characters of tools and a wrong price in llms.txt |
| LedgerCost analyst | 2/5 Free to read, no price per token anywhere | 2/5 A tenfold price gap between llms.txt and the plan data |
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.
Scrapeless
Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package and SDKs in three languages, all released between August and October 2026. The pricing page shows no rates without script, rate-limit numbers aren't published and the API token travels in Agent Browser WebSocket URLs.
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
Scrapeless
- Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
- Call browser_close when done so the session and its billing stop
- Set limit on crawl_start. Unset, it defaults to 10,000 pages
- Poll /result/{taskId} every 1 to 5 seconds after a 201, and back off when a call returns 429
- Fetch AI Scraper results within 5 minutes or set a webhook, since an unfetched result is still billed
Questions
Which is better for AI agents, Jina Reader or Scrapeless?
Scrapeless scores 58.1 (C) on agent readiness against Jina Reader's 54.1 (C), and leads in 2 of 7 scored categories. Jina Reader leads on schema & documentation and agent ergonomics.
Do Jina Reader and Scrapeless need an API key?
Jina Reader takes an API key or an OAuth sign-in. Scrapeless needs an API key.
Can an agent call Jina Reader and Scrapeless without installing anything?
Yes. Jina Reader has a hosted endpoint at https://r.jina.ai/ and Scrapeless at https://api.scrapeless.com.
Are Jina Reader and Scrapeless open source?
Jina Reader is open source (Apache-2.0). No open-source release is listed for Scrapeless.
Other comparisons with Jina Reader or Scrapeless
- Apify MCP Server vs Jina Reader
- Bright Data vs Jina Reader
- Bright Data vs Scrapeless
- BrowserAct vs Jina Reader
- BrowserAct vs Scrapeless
- Context.dev vs Jina Reader
- Context.dev vs Scrapeless
- Crawl4AI vs Jina Reader
- Crawl4AI vs Scrapeless
- fastCRW vs Jina Reader
- fastCRW vs Scrapeless
- Decodo Web Data API vs Jina Reader
- Decodo Web Data API vs Scrapeless
- Diffbot vs Jina Reader
- Diffbot vs Scrapeless
- 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 ScrapeGraphAI
- 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 Scrapeless
- Olostep vs Scrapeless
- Outcrawl vs Scrapeless
- Oxylabs Web Scraper API vs Scrapeless
- Scrape.do vs Scrapeless
- ScrapeGraphAI vs Scrapeless
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- Firecrawl MCP vs Jina Reader
- Firecrawl MCP vs Scrapeless
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
Machine-readable
- This page as Markdown
/compare/jina-reader-vs-scrapeless.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jina-reader.json·/api/v1/tools/scrapeless.json - From a terminal
anchor compare jina-reader scrapeless(the CLI) - Over MCP
compare_tools {"a": "jina-reader", "b": "scrapeless"}at/mcp, no key