Head to head · Scraping · October 2026 research run

Jina Reader vs ScrapingAnt

Jina Reader scores 54.1 (C) on agent readiness against ScrapingAnt's 42.5 (E), and leads in 6 of 7 scored categories. ScrapingAnt leads on payments & pricing. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons

Which one, for what

Jina Reader C

Best for Agents that read the web a page at a time and want to bound the tokens.

Ahead on

  • Reliability, 70 against 35
  • Schema & documentation, 77 against 46
  • Agent ergonomics, 80 against 72
  • Security & auth, 32 against 20
  • Maintenance & community, 45 against 5
  • Transparency & trust, 62 against 56

Also in its favour

  • Open source

Watch for

No price per token in any currency on the public page

ScrapingAnt E

Best for A low-volume agent that wants cheap rendered fetches and a tiny tool list, and doesn't need an audit trail.

Ahead on

  • Payments & pricing, 60 against 53

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where Jina Reader loses 7 points for them

Watch for

API Basics puts the key in the query string, so it lands in logs

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 Jina Reader +40

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).

ScrapingAnt 5

No changelog or dated API change found. The newest dated release of any vendor package is the GitHub Action v1.0.0, tagged 3 April 2026 (222 days), and the newest SDK is Python 2.1.0, tagged 16 July 2024 (0). No releases in the last 90 days (0). No public changelog. Support by email (3 of 15). The JavaScript client was last tagged v0.2.1 on 6 May 2022, so the SDKs aren't current, and no registry page shows ScrapingAnt's own MCP server (0). The Python client has a code-check workflow, but neither SDK has moved in over two years (2 of 10). 0 + 0 + 3 + 0 + 2 = 5.

Reliability Jina Reader +35

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).

ScrapingAnt 35

No status page linked from the site or docs (0). No readable incident history (5). The free plan allows 1 concurrent request and paid plans have no concurrency cap, with timeout settable from 5 to 60 seconds. No per-minute limits published (8 of 15). The rewritten errors page gives each status a retry rule, tells free-plan callers hitting the 409 concurrency limit to wait for the active request and queue, allows only bounded retries for 404, 423 and 500, and advises a small attempt cap with increasing delays and jitter for temporary failures on operations safe to repeat, and warns that a timed-out POST, PUT or DELETE may already have reached the target, with no idempotency keys and no 429 or Retry-After (12, backoff plus safe-retry guidance, as scrapingdog). No SLA found (0). The API is generally available (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.

Schema & documentation Jina Reader +31

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).

ScrapingAnt 46

No OpenAPI or Swagger spec found. The MCP docs give a typed parameter table for the 3 tools (8 of 25). docs.scrapingant.com/llms.txt still returns 404 and no Markdown twins were found (0). MCP descriptions are one line each, such as Fetch a URL and return raw HTML content, with no when-to-use guidance (8 of 20). Few parameters, typed, with proxy_type as an enum of datacenter or residential (10 of 15). Request examples on every docs page, and an errors page that now gives each status code its exact detail text, cause and retry rule, plus a separate SDK errors page (15). Versioned paths (v1 and v2) and no changelog (5 of 15). 8 + 0 + 8 + 10 + 15 + 5 = 46.

Security & auth Jina Reader +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).

ScrapingAnt 20

One account API key with no scopes. A new docs page explains how to regenerate it from the profile page, after which the old key answers 403 and an email confirms the change, so it is a plain revocable key (20). API Basics still tells you to send x-api-key as a query parameter, a documented option, so less 10 (10 of 30). The hosted MCP server now also accepts an OAuth sign-in bound to the active key. No read-only mode, and /v2/general can send POST, PUT and DELETE to target sites with no confirmation step; an IP allow-list can restrict where the key is used (5 of 20). No prompt-injection guidance found for the HTML, Markdown or text it returns (0 of 15). The Ant-credits-cost header and a subscription status endpoint show spend per call. No request log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). 10 + 5 + 0 + 5 + 0 = 20.

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).

ScrapingAnt 72

3 compact MCP tools (25). Markdown and text endpoints, AI extraction, wait-for-selector and a JSON extended response, but no output-size limit on the MCP tools (12 of 20). The errors page lists 7 statuses with exact detail messages, separates ScrapingAnt's status from the target's (Ant-page-status-code), and says for each whether to retry and what to fix (20, as scrapingdog). Requests are reads of third-party pages and failures aren't billed, but there are no idempotency keys or tool annotations (5 of 20). Only url is required, though browser defaults to true at 10 credits. Python and JavaScript clients exist but are stale (10 of 15). 25 + 12 + 20 + 5 + 10 = 72.

Payments & pricing ScrapingAnt +7

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.

ScrapingAnt 60

No x402, MPP or L402 (0). Credit costs per request type (1 to 125) and plan prices, Enthusiast $19 to Business Pro $599 and Custom from $699 a month, are public (20). 10,000 free credits a month, no card (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightJina ReaderScrapingAntEdge
Reliability16%7035Jina Reader +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7746Jina Reader +31
Agent ergonomics13%8072Jina Reader +8
Security & auth14%3220Jina Reader +12
Payments & pricing10%5360ScrapingAnt +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%455Jina Reader +40
Transparency & trust7%6256Jina Reader +6
Negative events≤15-70
TotalC 54.1/100E 42.5/100

Facts side by side

FactJina ReaderScrapingAnt
KindHTTP APIHTTP API
VendorJina AI (Elastic)ScrapingAnt (DATAANT)
Hosted endpointhttps://r.jina.ai/https://api.scrapingant.com/v2/general
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0none
Tools exposednone3
Read-only variant documentednono
llms.txtnono
Last release2026-10-232024-07-16
Terms last updated2026-05-04no date given
Privacy policy last updated2026-09-07no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity12k starsnone
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ScrapingAnt higher, the other way from the total score.

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.

ScrapingAnt

10,000 free credits a month with no card, three compact MCP tools, and an errors reference that tells an agent when to retry and what to fix. API Basics still puts the key in the query string, there's no status page or changelog, and no vendor package has had a release in over 180 days.

Before you call either

Jina Reader

  1. Prefix the URL, https://r.jina.ai/https://example.com, and read the Markdown
  2. Send x-max-tokens to cap a page, or x-token-budget to refuse one that's too big
  3. Use x-target-selector when you need one part of a page
  4. Keyless is 20 requests a minute and can't search. Add a key for loops or s.jina.ai
  5. On a 429, wait the retryAfter seconds in the error body before retrying

ScrapingAnt

  1. Send the key in the x-api-key header rather than the query string
  2. Use /v2/markdown for LLM input, and set browser=false on static pages to pay 1 credit instead of 10
  3. Switch to proxy_type=residential only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits
  4. On the free plan a second concurrent request gets 409. Queue requests and wait for the first to finish rather than retrying
  5. Google, Bing and Yandex result pages come back as raw HTML through /v2/general, so you parse them yourself

Questions

Which is better for AI agents, Jina Reader or ScrapingAnt?

Jina Reader scores 54.1 (C) on agent readiness against ScrapingAnt's 42.5 (E), and leads in 6 of 7 scored categories. ScrapingAnt leads on payments & pricing.

Do Jina Reader and ScrapingAnt need an API key?

Jina Reader takes an API key or an OAuth sign-in. ScrapingAnt needs an API key.

Can an agent call Jina Reader and ScrapingAnt without installing anything?

Yes. Jina Reader has a hosted endpoint at https://r.jina.ai/ and ScrapingAnt at https://api.scrapingant.com/v2/general.

Are Jina Reader and ScrapingAnt open source?

Jina Reader is open source (Apache-2.0). No open-source release is listed for ScrapingAnt.

Other comparisons with Jina Reader or ScrapingAnt

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.