# Jina Reader vs ScrapeOps Proxy API Aggregator (slim)

> Jina Reader scores 51.9 (D) to ScrapeOps Proxy API Aggregator's 50.4 (D) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/jina-reader-vs-scrapeops.md (~4,600 tokens) · this version ~1,830 tokens · JSON https://www.anchorterminal.com/compare/jina-reader-vs-scrapeops.json · canonical https://www.anchorterminal.com/compare/jina-reader-vs-scrapeops
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Jina Reader scores 51.9 (D) on agent readiness against ScrapeOps Proxy API Aggregator's 50.4 (D), and leads in 5 of 7 scored categories. ScrapeOps Proxy API Aggregator leads on payments & pricing. Both do scraping.

- Jina Reader: D 51.9, rank #999 of 1486 · https://www.anchorterminal.com/tools/jina-reader.min.md
- ScrapeOps Proxy API Aggregator: D 50.4, rank #1057 of 1486 · https://www.anchorterminal.com/tools/scrapeops.min.md
- Jina Reader, good for Agents that read the web a page at a time and want to bound the tokens. Ahead on Reliability, 70 against 37; Schema & documentation, 77 against 67. Also Open source.
- ScrapeOps Proxy API Aggregator, good for Teams that want one key across many proxy APIs, paid only on success, with cost caps per request. Ahead on Payments & pricing, 40 against 35. Also Runs on your own machine; Free to start without a card; No incidents deducted, where Jina Reader loses 7 points for them.

| Category | Jina Reader | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Reliability (16%) | 70 | 37 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 67 |
| Agent ergonomics (13%) | 80 | 79 |
| Security & auth (14%) | 32 | 28 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 45 | 46 |
| Transparency & trust (7%) | 62 | 61 |

| Fact (where they differ) | Jina Reader | ScrapeOps Proxy API Aggregator |
| --- | --- | --- |
| Vendor | Jina AI (Elastic) | ScrapeOps Limited |
| Hosted endpoint | `https://r.jina.ai/` | `https://mcp.scrapeops.io/mcp` |
| Transports | HTTP, Streamable HTTP | stdio, Streamable HTTP |
| Pricing | Pay per use | Freemium |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 3 |
| llms.txt | no | yes |
| Last release | 2026-10-23 | 2026-10 |
| Terms last updated | 2026-05-04 | no date given |
| Privacy policy last updated | 2026-09-07 | no date given |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 12k stars | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Reliability, Jina Reader +33: 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).); ScrapeOps Proxy API Aggregator 37 (Graded on the hosted lines. No status page was found on scrapeops.io or in the docs, and status.scrapeops.io did not answer (0). No readable incident history (5). Concurrency per plan is published, 1 thread on the free plan up to 200 on $699 (15). 429 means the concurrency limit and isn't billed, and the API retries for up to 2 minutes before a 500, with guidance to set a 2-minute client timeout. No Retry-After or backoff guidance (7 of 15). No SLA; the terms disclaim availability (0). Generally available since July 2022 (10). 0 + 5 + 15 + 7 + 0 + 10 = 37.)
- Schema & documentation, Jina Reader +10: 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).); ScrapeOps Proxy API Aggregator 67 (No OpenAPI or similar spec. The MCP server's three tools have typed inputs in its source (10 of 25). llms.txt and llms-full.txt index the docs for models (10). Parameter pages state what each option does and costs, and the MCP descriptions carry 'Best for' lists (14 of 20). Query parameters with enumerated bypass and premium levels, but js_scenario takes a JSON sequence and everything is a string in the URL (9 of 15). Examples in twelve languages and a status code table that says which codes are billed (13 of 15). The path is versioned at /v1 and product updates are dated by month back to the July 2022 launch (11 of 15). 10 + 10 + 14 + 9 + 13 + 11 = 67.)
- Payments & pricing, ScrapeOps Proxy API Aggregator +5: Jina Reader 35 (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).); ScrapeOps Proxy API Aggregator 40 (No x402, MPP or L402 (0). Credit costs per option and all twelve plan prices are public (20). Free plan of 1,000 credits a month with no card (20). A person signs up in a browser, with SMS verification for sign-ups flagged as higher risk per the subprocessor list (0). 0 + 20 + 20 + 0 = 40.)