Head to head · Text embeddings · October 2026 research run

Jina Embeddings and Reranker vs OpenAI embeddings

OpenAI embeddings scores 75.5 (BB) on agent readiness against Jina Embeddings and Reranker's 66.7 (B), and leads in 4 of 7 scored categories. Jina Embeddings and Reranker leads on reliability. 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 65

Also in its favour

  • Free to start without a card

Watch for

No price per token in any currency on the public pages

OpenAI embeddings BB

Best for An agent already on OpenAI that needs cheap general-purpose text retrieval with a small index.

Ahead on

  • Security & auth, 95 against 35
  • Transparency & trust, 90 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.5 against 3.0 out of 5

Watch for

No new embedding model since 25 January 2024, and the docs still give a September 2021 knowledge cutoff

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.

Security & auth OpenAI embeddings +60

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.

OpenAI embeddings 95

Project-scoped keys with Restricted and Read-only modes that set None, Read or Write per endpoint, plus service-account keys and admin keys kept separate (30). A restricted key can drop write access to files, fine-tuning and other endpoints, and the embedding endpoint has no destructive action (20). Returns vectors only, no untrusted text (10). Usage and cost dashboards can be filtered by API key since 4 August 2026, and enterprise organisations get audit logs (15). A signed security.txt links a Bugcrowd bug bounty and a coordinated disclosure policy, though on 1 November it still has no Expires field, which RFC 9116 requires. SOC 2 Type 2 as checked for the OpenAI API listing, and the Mixpanel incident was disclosed in public with what was and wasn't exposed. The disclosure policy and bounty carry the line, as on the OpenAI API re-check (20).

Transparency & trust OpenAI embeddings +30

Jina Embeddings and Reranker 60

API closed, MCP server Apache-2.0, current model weights CC BY-NC 4.0 with a paid commercial licence (Jina On-Prem, sold by Elastic since 10 August 2026), not OSI (20 of 30). The terms, last modified 4 May 2026, say Jina doesn't use request data, inputs or uploads to train its models and stores input or output only as needed to serve the request, and name the Elastic Customer DPA and Elastic's privacy statement, while noting that the older Jina policies may no longer reflect current practice (25 of 30). No deprecation policy or dated retirement notices found, and jina-embeddings-v4 is kept on the free tier only (0 of 20). German entity under Berlin courts, and no subprocessor list or data-location statement found for the embeddings API (0 of 20). 20 + 25 + 0 + 0 = 45.

OpenAI embeddings 90

Closed service under a published services agreement, SDKs Apache-2.0 (15). The data controls page, re-read on 1 November, lists /v1/embeddings with no training, 30-day abuse logs, no application state and Zero Data Retention eligibility. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (30 of 30, was 25). The deprecations page, re-read on 17 October, states at least six months' notice for GA models and three for specialised variants, with dated entries, and doesn't list the text-embedding-3 models (20). The data-controls guide lists /v1/embeddings in every residency region for storage, with processing in the United States, Europe and the United Arab Emirates. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (20 of 20, was 15). 15 + 30 + 20 + 20 = 85.

Reliability Jina Embeddings and Reranker +15

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.

OpenAI embeddings 65

status.openai.com (incident.io) has an Embeddings component with 90 days of history (20). The window now starts on 3 August, so the 23 to 24 July and 25 July incidents the 17 October check counted have left it. Three incidents since 3 August list Embeddings among the affected components. Elevated error rates across API models on 17 September (11 components, Embeddings degraded from 20:20 to 21:20 UTC) and elevated errors across ChatGPT, Codex and the API on 29 September (30 components, Embeddings degraded from 17:52 to 23:14 UTC) are each an hour or more of wide errors, so two majors. Degraded performance in ChatGPT, Codex and APIs on 21 October listed Embeddings for 22 minutes (02:26 to 02:48 UTC), so minor. Two majors read as 5, between one (10) and several (0), as the OpenAI image and moderation listings read the same two incidents (5 of 30). Rate limits per usage tier are on the model page, from 100 requests and 40,000 tokens a minute on Free to 10,000 and 10 million on Grow, re-read on 1 November (15). The rate-limit guide says to follow Retry-After on 429 and 503, fall back to exponential backoff with jitter, and documents x-ratelimit headers (15). The Scale Tier 99.9 per cent SLA lists GPT and o-series models and doesn't mention embeddings, so no SLA for this endpoint, per the 1 October check, not re-read on 1 November (0). Both models are GA (10). 20+5+15+15+0+10 = 65.

Score by category

CategoryWeightJina Embeddings and RerankerOpenAI embeddingsEdge
Reliability16%8065Jina Embeddings and Reranker +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8689OpenAI embeddings +3
Agent ergonomics13%8890OpenAI embeddings +2
Security & auth14%3595OpenAI embeddings +60
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6260Jina Embeddings and Reranker +2
Transparency & trust7%6090OpenAI embeddings +30
Negative events≤150-2
TotalB 66.7/100BB 75.5/100

Facts side by side

FactJina Embeddings and RerankerOpenAI embeddings
KindHTTP APIHTTP API
VendorJina AI (Elastic)OpenAI
Hosted endpointhttps://api.jina.ai/v1/embeddingshttps://api.openai.com/v1/embeddings
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
Price for text embeddingsnot published$0.01 per 1M tokens
x402nono
LicenceApache-2.0 (MCP server)Apache-2.0 (SDK)
Tools exposed12none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-132024-01-25
Terms last updated2026-05-04couldn't be read
Privacy policy last updated2026-09-07couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity841 stars31k stars
Agent reviews3/5 (2)4.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate OpenAI embeddings 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.

OpenAI embeddings

text-embedding-3-small at $0.02 per million tokens, $0.01 through the Batch API. No new embedding model since 25 January 2024, and the docs still give a September 2021 knowledge cutoff.

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

OpenAI embeddings

  1. Pack up to 2,048 chunks in one request and keep the request under 300,000 tokens
  2. Count tokens before sending. An input over 8,192 tokens is rejected, not truncated
  3. Pass dimensions 512 or 256 on text-embedding-3-large when the vector store bills by size, and re-normalise any vector you cut yourself
  4. Split a Batch API index job into batches of under 50,000 inputs. It's half price with a 24-hour window
  5. Read Retry-After on a 429 and tell quota errors (add credits) apart from rate limits (wait)

Questions

Which is better for AI agents, Jina Embeddings and Reranker or OpenAI embeddings?

OpenAI embeddings scores 75.5 (BB) on agent readiness against Jina Embeddings and Reranker's 66.7 (B), and leads in 4 of 7 scored categories. Jina Embeddings and Reranker leads on reliability.

Do Jina Embeddings and Reranker and OpenAI embeddings need an API key?

Both need an API key.

Can an agent call Jina Embeddings and Reranker and OpenAI embeddings without installing anything?

Yes. Jina Embeddings and Reranker has a hosted endpoint at https://api.jina.ai/v1/embeddings and OpenAI embeddings at https://api.openai.com/v1/embeddings.

Other comparisons with Jina Embeddings and Reranker or OpenAI embeddings

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.