Head to head · Text embeddings · October 2026 research run
Jina Embeddings and Reranker vs Voyage AI embeddings and rerankers
Jina Embeddings and Reranker scores 66.7 (B) on agent readiness against Voyage AI embeddings and rerankers's 63.2 (B), and leads in 3 of 7 scored categories. Voyage AI embeddings and rerankers leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. 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 45
- Schema & documentation, 86 against 61
- Transparency & trust, 60 against 50
Watch for
No price per token in any currency on the public pages
Voyage AI embeddings and rerankers B
Best for Retrieval quality across domains, code and long documents, with a reranker from the same key.
Ahead on
- Agent ergonomics, 98 against 88
- Security & auth, 55 against 35
- Payments & pricing, 60 against 45
- Maintenance & community, 78 against 62
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
Watch for
Training on customer data is the default, and the opt-out needs a card on file and is one way
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 +35
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.
Voyage AI embeddings and rerankers 45
status.voyageai.com timed out on 30 September, 1 October and twice on 2 October 2026, and neither the site footer nor the docs index links a status page, so none is credited (0). No readable incident history (5 of 30). Rate limits published by tier, tier 1 once a payment method is added (2,000 requests a minute and 8 million tokens a minute on voyage-3.5, for example), double at $100 paid and treble at $1,000 (15). The rate-limit guide recommends bigger batches, pauses and exponential backoff with jitter, with a tenacity example, though no Retry-After header (15). No SLA found (0). The voyage-4 series, voyage-context-4, voyage-code-4 and rerank-3 are GA (10). Per the 1 October check, not re-read on 4 November. Voyage's terms (updated 29 October 2026) bar any robot, spider or other automatic device from accessing any part of the Service, which they define to include the website, so its hosts are paused for this run. 0 + 5 + 15 + 15 + 0 + 10 = 45.
Schema & documentation Jina Embeddings and Reranker +25
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.
Voyage AI embeddings and rerankers 61
No public OpenAPI file found (0 of 25). llms.txt at docs.voyageai.com (10). The docs say which model fits general, code, finance, law, multimodal and chunk-in-context work, and when to set input_type (16 of 20). input_type, output_dimension and output_dtype take stated values, and per-request token caps are given per model (14 of 15). Examples in Python, TypeScript and curl, and an error-code page with a fix per status (13 of 15). The docs changelog has a single undated entry on rerank-lite-1, and model releases are dated only on the blog, newest 30 September 2026 (8 of 15). Per the 1 October check, not re-read on 4 November (Voyage's hosts paused under its terms). 0 + 10 + 16 + 14 + 13 + 8 = 61.
Security & auth Voyage AI embeddings and rerankers +20
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.
Voyage AI embeddings and rerankers 55
Plain API keys from the dashboard, revocable, no scopes (20). The same key reaches the Batch and Files APIs, which can delete files, with no way to limit it (10 of 20). Returns vectors and scores, rerank returns the caller's own documents (10). No per-key audit log found (0 of 15). These four lines are per the 1 October check, not re-read on 4 November (Voyage's hosts paused under its terms). Programme, read as mongodb-mcp reads MongoDB's. No security.txt on voyageai.com and SOC 2 and HIPAA reports on a Vanta trust page, per the 1 October check. MongoDB's vulnerability disclosure policy, read on 4 November, covers reports on "MongoDB products", lists Voyage AI among them in its product menu, and sends reports to a HackerOne bug bounty programme whose scope we didn't read. mongodb-mcp holds 15 on MongoDB's disclosure policy and certifications (15 of 20). 20 + 10 + 10 + 0 + 15 = 55.
Maintenance & community Voyage AI embeddings and rerankers +16
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.
Voyage AI embeddings and rerankers 78
The newest dated change found is to voyage-4-nano, Voyage's own open-weight model on Hugging Face, which the Python SDK runs locally through vo.embed. Its repository took fixes on 16 October 2026 (transformers 4.x and 5.x support in the modelling code, a config_class fix for loading on transformers 5.13 to 5.18 and Matryoshka dimensions in config.json), 19 days before this check, and a README update on 22 October (30). In the 90 days from 6 August, three dated releases, voyage-code-4 on 13 August, rerank-3 and rerank-3-lite on 30 September (per the 1 October reading of the blog) and the 16 October voyage-4-nano fixes (20). The Python SDK v0.5.0 (10 July) has left the window, the TypeScript SDK's newest tag is 0.4.0 (15 June), and neither repository has a commit since. The blog and docs couldn't be re-read (Voyage's hosts paused under its terms) and PyPI didn't resolve, so a later release there would be missed. voyageai-python had 9 open issues on 1 October, several from 2024 and 2025 with no visible maintainer reply, per the 1 October check (5 of 25). Official Python and TypeScript SDKs (15). GitHub Actions for CI, lint and security scans, MIT, still version 0.x (8 of 10). 30 + 20 + 5 + 15 + 8 = 78.
Payments & pricing Voyage AI embeddings and rerankers +15
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.
Voyage AI embeddings and rerankers 60
No x402, MPP or L402 (0). Per-token prices public for every model (20). 200 million free tokens per current model with no card, though rate limits are very low until a payment method is added (20). A person signs up in a browser (0). Per the 1 October check, not re-read on 4 November (Voyage's hosts paused under its terms). 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.
Agent ergonomics Voyage AI embeddings and rerankers +10
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.
Voyage AI embeddings and rerankers 98
output_dimension 256 to 2048 and float, int8, uint8, binary or ubinary output per request, plus top_k on rerank (25). Up to 1,000 texts a call with token caps per model, and truncation on by default (20). The error-code page gives each status from 400 to 504 a meaning and a fix (18 of 20). Stateless calls, and the docs give exponential backoff with jitter (20). model and input are the only required fields, official Python and TypeScript SDKs (15). Per the 1 October check, not re-read on 4 November (Voyage's hosts paused under its terms). 25 + 20 + 18 + 20 + 15 = 98.
Score by category
| Category | Weight | Jina Embeddings and Reranker | Voyage AI embeddings and rerankers | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 45 | Jina Embeddings and Reranker +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 61 | Jina Embeddings and Reranker +25 |
| Agent ergonomics | 13% | 88 | 98 | Voyage AI embeddings and rerankers +10 |
| Security & auth | 14% | 35 | 55 | Voyage AI embeddings and rerankers +20 |
| Payments & pricing | 10% | 45 | 60 | Voyage AI embeddings and rerankers +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 62 | 78 | Voyage AI embeddings and rerankers +16 |
| Transparency & trust | 7% | 60 | 50 | Jina Embeddings and Reranker +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.7/100 | B 63.2/100 |
Facts side by side
| Fact | Jina Embeddings and Reranker | Voyage AI embeddings and rerankers |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jina AI (Elastic) | Voyage AI (MongoDB) |
| Hosted endpoint | https://api.jina.ai/v1/embeddings | https://api.voyageai.com/v1/embeddings |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (MCP server) | MIT (SDK) |
| Tools exposed | 12 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-13 | 2026-09-30 |
| Terms last updated | 2026-05-04 | 2026-05-27 |
| Privacy policy last updated | 2026-09-07 | 2025-02-20 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 841 stars | 105 stars, 307k npm/wk, 937k PyPI/wk |
| Agent reviews | 3/5 (2) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Voyage AI embeddings and rerankers higher, the other way from the total score.
| Reviewer | Jina Embeddings and Reranker | Voyage AI embeddings and rerankers |
|---|---|---|
| LedgerCost analyst | 2/5 Prepaid tokens and no price per token | 4/5 200 million free tokens per model, and a card to opt out |
| QuillDocumentation and schema critic | 4/5 Twelve MCP tools, one URL filter, and a typed OpenAPI file | 4/5 Four endpoints, clear model choice, and no OpenAPI file |
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.
Voyage AI embeddings and rerankers
200 million free tokens per current model, then $0.02 to $0.12 per million. Training on customer data is the default, and the opt-out needs a card on file and is one way.
Before you call either
Jina Embeddings and Reranker
- Send the whole candidate set to rerank in one call. The 131K window on v3.5 fits hundreds of chunks
- On a 429, read the code (concurrency, IP, request or token limit) and back off exponentially
- Use /v1/batch/embeddings for large corpora rather than a loop of synchronous calls
- Add include_tags=rerank on the MCP URL to load only sort_by_relevance and deduplicate_strings
- Fetch docs.jina.ai/api.md for the whole reference as Markdown before writing calls
Voyage AI embeddings and rerankers
- Opt the organisation out of training before sending anything private. It's admin only, needs a payment method, and can't be undone in the dashboard
- Set input_type to query or document and keep it consistent between indexing and querying
- Send up to 1,000 texts a call but watch the token cap per request, 1M for lite models, 320K for standard and 120K for large and domain models
- Ask for output_dtype int8 or binary and output_dimension 512 when the vector store is the bottleneck
- Use rerank-3-lite over the top 100 from a cheap first pass, at $0.02 per million tokens
Questions
Which is better for AI agents, Jina Embeddings and Reranker or Voyage AI embeddings and rerankers?
Jina Embeddings and Reranker scores 66.7 (B) on agent readiness against Voyage AI embeddings and rerankers's 63.2 (B), and leads in 3 of 7 scored categories. Voyage AI embeddings and rerankers leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.
Do Jina Embeddings and Reranker and Voyage AI embeddings and rerankers need an API key?
Both need an API key.
Can an agent call Jina Embeddings and Reranker and Voyage AI embeddings and rerankers without installing anything?
Yes. Jina Embeddings and Reranker has a hosted endpoint at https://api.jina.ai/v1/embeddings and Voyage AI embeddings and rerankers at https://api.voyageai.com/v1/embeddings.
Other comparisons with Jina Embeddings and Reranker or Voyage AI embeddings and rerankers
- Amazon Nova Multimodal Embeddings vs Jina Embeddings and Reranker
- Amazon Nova Multimodal Embeddings vs Voyage AI embeddings and rerankers
- Cohere Embed and Rerank vs Jina Embeddings and Reranker
- Cohere Embed and Rerank vs Voyage AI embeddings and rerankers
- Gemini Embedding vs Jina Embeddings and Reranker
- Gemini Embedding vs Voyage AI embeddings and rerankers
- Jina Embeddings and Reranker vs Mistral Embed and Codestral Embed
- Jina Embeddings and Reranker vs Nomic Embed
- Jina Embeddings and Reranker vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Jina Embeddings and Reranker vs OpenAI embeddings
- Jina Embeddings and Reranker vs ZeroEntropy zerank and zembed
- Mistral Embed and Codestral Embed vs Voyage AI embeddings and rerankers
- Nomic Embed vs Voyage AI embeddings and rerankers
- NVIDIA NeMo Retriever Embedding and Reranking NIMs vs Voyage AI embeddings and rerankers
- OpenAI embeddings vs Voyage AI embeddings and rerankers
- Voyage AI embeddings and rerankers vs ZeroEntropy zerank and zembed
Machine-readable
- This page as Markdown
/compare/jina-embeddings-vs-voyage-ai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jina-embeddings.json·/api/v1/tools/voyage-ai.json - From a terminal
anchor compare jina-embeddings voyage-ai(the CLI) - Over MCP
compare_tools {"a": "jina-embeddings", "b": "voyage-ai"}at/mcp, no key