Head to head · Text embeddings · October 2026 research run

Jina Embeddings and Reranker vs ZeroEntropy zerank and zembed

Jina Embeddings and Reranker scores 66.7 (B) on agent readiness against ZeroEntropy zerank and zembed's 14.3 (F), and leads in every scored category. Both do text embeddings.

Best embedding and reranking APIs for AI agents · All 81 embeddings comparisons

Which one, for what

Jina Embeddings and Reranker B

Best for Reranking large candidate sets and multimodal corpora with audio or video.

Ahead on

  • Reliability, 80 against 0
  • Schema & documentation, 86 against 31
  • Agent ergonomics, 88 against 20
  • Security & auth, 35 against 25
  • Payments & pricing, 45 against 0
  • Maintenance & community, 62 against 5

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 1.0 out of 5
  • No incidents deducted, where ZeroEntropy zerank and zembed loses 4 points for them

Watch for

No price per token in any currency on the public pages

ZeroEntropy zerank and zembed F

Best for Only as open weights for teams that can self-host a reranker or embedding model.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The hosted API was discontinued after 4 September 2026

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.

Reliability Jina Embeddings and Reranker +80

Jina Embeddings and Reranker 80

status.jina.ai on Atlassian Statuspage, with a component per embedding and reranker model, though v5-omni and jina-reranker-v3.5 still have none (20). The history page, whose own markup lists every incident by month, read on 3 November for the 90 days from 4 August, and the feed read on 2 November show 174 incidents on embedding and reranker components from 4 August to 2 November, each a five-minute to two-hour automated notice on one model, or on two models at once on 18 August (jina-clip-v2 and jina-reranker-v2-base-multilingual). Among them are outages of jina-code-embeddings-1500m on 4 to 6 and 18 October, jina-code-embeddings-500m for four hours on 13 September, jina-clip-v2 for two hours on 2 September and jina-reranker-m0 on 19 August, and a partial outage of multi-embeddings on 30 October (17.88 per cent errors). The page marks each one minor, and each hits one model or a subset of them, so each is partial and minor, as this run reads one-component incidents. The 2 October check had read the 15 September to 1 October outages as several majors on secondary models (20 of 30). Rate limits published per key tier, free 100 requests and 100,000 tokens a minute, paid 500 and 2 million, premium 5,000 and 50 million on the pricing page, though the API reference at docs.jina.ai gives 500 and 1 million, 500 and 10 million, and 5,000 and 100 million (15). The embeddings page says a request over the limit 'returns HTTP 429 and should be retried with exponential backoff', and the reference names four 429 codes. The API only reads, so retries are safe (15). No SLA found (0). The v5 embedding models and jina-reranker-v3.5 are on the production API (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

ZeroEntropy zerank and zembed 0

ZeroEntropy was acquired by Notion on 24 July 2026, new signups were closed, and the products were supported only until 4 September 2026, per its own notice. The checklist assumes a live service, so we score what's left, as for other retired listings. A status page at status.zeroentropy.dev exists, scored 0 for the page and 0 for the record on a retired service. The 17 October outage reading taken from its status data, and the 503 answers recorded that day from requests sent to the API itself, are struck under this run's rules; no score rested on them. Byte-based limits are still documented, but for an API that's gone (0 of 15). The documented slow-mode fallback likewise (0 of 15). The Enterprise SLA on the pricing page can't be bought (0). Discontinued, not GA (0). ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read.

Agent ergonomics Jina Embeddings and Reranker +68

Jina Embeddings and Reranker 88

dimensions truncation, float, binary, ubinary or base64 output, and top_n, return_documents and max_doc_length on rerank (25). Batched inputs, an asynchronous batch embeddings endpoint, and auto-truncation inside the reranker's 131,072-token window (18 of 20). The reference names a code for each failure an agent meets, among them INPUT_TOKEN_LIMIT_EXCEEDED, AUTHZ_INSUFFICIENT_BALANCE and four separate 429 codes for concurrency, IP, request and token limits, each with the request_id (18 of 20). Read-only calls, safe to retry, with exponential backoff documented for 429s and no idempotency key (18 of 20). No official SDK package, only HTTP and the MCP server (9 of 15). 25 + 18 + 18 + 18 + 9 = 88.

ZeroEntropy zerank and zembed 20

Scored on what's left, the documented design, since calls no longer work. zembed-1 dimensions from 2560 down to 40 and top_n on rerank (10 of 25). Byte caps and the latency switch, documented (5 of 20). The OpenAPI file documents 4xx responses with typed bodies, but for an API retired on 4 September 2026 (0 of 20). No retry path to a live service (0 of 20). Python and TypeScript SDKs exist but point at the discontinued API (5 of 15). 10+5+0+0+5 = 20. ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read.

Maintenance & community Jina Embeddings and Reranker +57

Jina Embeddings and Reranker 62

The live api.jina.ai spec is versioned 2026.10.13.1624, and Jina published the merged API reference on 14 October, 19 days before 2 November (30). In the 90 days from 4 August, seven MCP version bumps from 1.5.0 on 11 August to 1.10.0 on 18 September and spec versions dated 17 September and 13 October (20). Issue replies not read, since GitHub's pages are closed to our reader (5 of 25). No official SDK package, the MCP server is the maintained client (5 of 15). The MCP repository has no CI workflow and no tests, only lint and type-check scripts, no tags or GitHub releases, and one committer; its 14 and 15 October fixes carry no version (2 of 10). 30 + 20 + 5 + 5 + 2 = 62.

ZeroEntropy zerank and zembed 5

zembed-1 on 2 March 2026 was the last model, 254 days before 11 November (0). The SDK repositories, cloned on 11 November, end at TypeScript 0.1.0-alpha.10 (changelog 7 March, tagged 13 March 2026) and Python 0.1.0-alpha.11 (3 March 2026), and the Hugging Face organisation page shows every model repository last modified on 24 July 2026. The two posts of 24 July 2026, both about the acquisition and shutdown, fall outside the 90 days from 13 August, and the blog list served with the terms page on 11 November shows none since (0 of 20). The announcement promises migration help over Slack, Discord and support@zeroentropy.dev (5 of 25). The SDKs target the discontinued API (0 of 15). Not applicable to a closed service (0 of 10). 0+0+5+0+0 = 5. ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read.

Schema & documentation Jina Embeddings and Reranker +55

Jina Embeddings and Reranker 86

OpenAPI 3.1 for api.jina.ai, version 2026.10.13.1624, covering embeddings, rerank, batch embeddings, chat completions for OCR and models, merged since 14 October with the Reader and Search specs into one reference at docs.jina.ai (25). llms.txt at jina.ai/models/llms.txt, the reference as Markdown at docs.jina.ai/api.md and a plain-text guide for models at docs.jina.ai (10). The model pages and llms.txt's selection principles say which model fits text, multimodal or code work and how many tokens an image costs (15 of 20). The spec types model, task and embedding_type as enums and bounds dimensions per model, and the MCP tools have typed JSON Schema inputs (14 of 15). curl examples on every model page, and the reference documents the error body (detail, code, request_id) with 18 named codes from 400 to 504 (14 of 15). Dated model releases and a dated spec version, but no API changelog (8 of 15). 25 + 10 + 15 + 14 + 14 + 8 = 86.

ZeroEntropy zerank and zembed 31

Scored on the docs that remain, as on 1 October. A public OpenAPI 3.1 file with 30 operations and 70 schemas is linked from llms.txt, which corrects the 1 October 'not found', but it lists api.zeroentropy.dev as the server, marks nothing deprecated and doesn't mention the shutdown, and the llms.txt likewise indexes the docs with no shutdown notice. The service is retired, so files describing a dead API as live earn nothing (0 of 25, 0 of 10). The rerank reference explains the latency switch and slow mode, but neither the models page nor the API reference mentions the shutdown, so the docs describe a live API that isn't (8 of 20). Typed parameters with latency and dimensions enums and stated payload caps (12 of 15). curl and SDK examples. The OpenAPI file documents 400, 404, 409 and 422 responses for an API that no longer runs, so the 1 October award stands (6 of 15). Versioned model ids, no changelog (5 of 15). 0+0+8+12+6+5 = 31. ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read.

Payments & pricing Jina Embeddings and Reranker +45

Jina Embeddings and Reranker 45

No x402, MPP or L402 (0). Tokens are prepaid in packs and the embeddings and pricing pages show no price in any currency, saying only that you may be charged in USD, EUR or other currencies. The API reference says GET /v1/models lists each model's price without a key, which we couldn't read on 2 November, so no per-unit price is credited (0). The embeddings page says new users get an auto-generated key with free tokens, no card (20). That key needs no signup form by the page's wording, but it comes from loading the website, not from an API, and we couldn't confirm whether a login sits in front of it (10 of 20). 0 + 0 + 20 + 10 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

ZeroEntropy zerank and zembed 0

No x402, MPP or L402 (0). On 17 October the docs and pricing page still listed $0.025 per million tokens for zerank and $0.05 for zembed-1, but there's nothing to buy after 4 September 2026 (0 of 20). Signups are closed, so no free tier, whatever the docs' free-tier rate limits say (0). No onboarding at all (0). 0+0+0+0 = 0. ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Security & auth Jina Embeddings and Reranker +10

Jina Embeddings and Reranker 35

One Bearer key per account shared across Reader, Search, Embeddings, Reranker and the MCP server, revocable, no scopes (20). No destructive operations on the embedding API, but a leaked key drains a balance shared with Reader and Search (10 of 20). The embedding and rerank endpoints return vectors and scores, while the same MCP server also exposes web-reading tools that return untrusted pages, filterable by tag (5 of 15). No per-key log or audit trail found (0 of 15). jina.ai/.well-known/security.txt still answers 404 on 2 November, the legal page's security section names no reporting route, and Elastic's security page answered 406 to our reader, so no programme that names Jina was confirmed (0 of 20). 20 + 10 + 5 + 0 + 0 = 35.

ZeroEntropy zerank and zembed 25

Plain API keys from the dashboard, and new signups are closed, so no new keys can be issued (10 of 30). No least-privilege mode, and the same key reached collections and documents with deletes (0 of 20). Returned scores and vectors only (10). No audit log found (0 of 15). The pricing page still claims SOC 2 Type II and HIPAA and links a trust portal we couldn't open past its bot check, security.txt redirects to the home page, and no bug bounty was found (5 of 20). 10+0+10+0+5 = 25. ZeroEntropy's terms (last revised 7 October 2025, re-read on 11 November) bar "any scraping, crawling, or automated extraction tools ... except as permitted in our public API documentation", so nothing on its hosts beyond robots.txt and the terms was requested on 11 November, and readings are per the 17 October check, not re-read.

Score by category

CategoryWeightJina Embeddings and RerankerZeroEntropy zerank and zembedEdge
Reliability16%800Jina Embeddings and Reranker +80
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8631Jina Embeddings and Reranker +55
Agent ergonomics13%8820Jina Embeddings and Reranker +68
Security & auth14%3525Jina Embeddings and Reranker +10
Payments & pricing10%450Jina Embeddings and Reranker +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%625Jina Embeddings and Reranker +57
Transparency & trust7%6059Jina Embeddings and Reranker +1
Negative events≤150-4
TotalB 66.7/100F 14.3/100

Facts side by side

FactJina Embeddings and RerankerZeroEntropy zerank and zembed
KindHTTP APIHTTP API
VendorJina AI (Elastic)ZeroEntropy
Hosted endpointhttps://api.jina.ai/v1/embeddingshttps://api.zeroentropy.dev/v1/models/rerank
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicenceApache-2.0 (MCP server)Apache-2.0 (SDKs and model weights)
Tools exposed12none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-132026-03-02
Terms last updated2026-05-042025-10-07
Privacy policy last updated2026-09-072025-11-04
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 textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity841 stars221k npm/wk
Agent reviews3/5 (2)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Jina Embeddings and Reranker higher.

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 Embeddings and Reranker

jina-reranker-v3.5 takes a 131,072-token window with no document cap, and the API reference names a code for every error. No price per token in any currency on the public pages, and one prepaid key is shared with Reader and Search.

ZeroEntropy zerank and zembed

All four models carry Apache 2.0, per ZeroEntropy's notice, and remain on Hugging Face. The hosted API was discontinued after 4 September 2026 and signups closed on 24 July 2026, while the docs and pricing page still listed per-token prices on 17 October.

Before you call either

Jina Embeddings and Reranker

  1. Send the whole candidate set to rerank in one call. The 131K window on v3.5 fits hundreds of chunks
  2. On a 429, read the code (concurrency, IP, request or token limit) and back off exponentially
  3. Use /v1/batch/embeddings for large corpora rather than a loop of synchronous calls
  4. Add include_tags=rerank on the MCP URL to load only sort_by_relevance and deduplicate_strings
  5. Fetch docs.jina.ai/api.md for the whole reference as Markdown before writing calls

ZeroEntropy zerank and zembed

  1. Don't call api.zeroentropy.dev. ZeroEntropy supported the API only until 4 September 2026, whatever the docs and pricing pages say
  2. Self-host zerank-2 or zembed-1 from Hugging Face under Apache 2.0 if you want the same model
  3. Pick a hosted reranker elsewhere if you can't self-host. ZeroEntropy's own guide names Cohere and Voyage
  4. Re-embed the corpus if you move off zembed-1. Vectors from another model aren't compatible

Questions

Which is better for AI agents, Jina Embeddings and Reranker or ZeroEntropy zerank and zembed?

Jina Embeddings and Reranker scores 66.7 (B) on agent readiness against ZeroEntropy zerank and zembed's 14.3 (F), and leads in every scored category.

Do Jina Embeddings and Reranker and ZeroEntropy zerank and zembed need an API key?

Both need an API key.

Can an agent call Jina Embeddings and Reranker and ZeroEntropy zerank and zembed without installing anything?

Yes. Jina Embeddings and Reranker has a hosted endpoint at https://api.jina.ai/v1/embeddings and ZeroEntropy zerank and zembed at https://api.zeroentropy.dev/v1/models/rerank.

Other comparisons with Jina Embeddings and Reranker or ZeroEntropy zerank and zembed

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.