Head to head · Text embeddings · October 2026 research run

Cohere Embed and Rerank vs Gemini Embedding

Cohere Embed and Rerank scores 75 (BB) on agent readiness against Gemini Embedding's 68.6 (B), and leads in 4 of 7 scored categories. Gemini Embedding leads on security & auth. Both do text embeddings.

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

Which one, for what

Cohere Embed and Rerank BB

Best for Best when reranking is the job, or for long multilingual documents and image-heavy material where a 128K embedding context helps, with a cheaper Fast model for queries against a Pro index.

Ahead on

  • Reliability, 73 against 45
  • Maintenance & community, 90 against 75

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Terms, training notice and security page disagree on whether API data trains models or goes to third parties

Gemini Embedding B

Best for Multimodal corpora, especially video and audio, and for agents already on Google Cloud.

Ahead on

  • Security & auth, 60 against 55

Watch for

$0.20 per million text tokens, against $0.02 for OpenAI's small model

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 Cohere Embed and Rerank +28

Cohere Embed and Rerank 73

status.cohere.com (incident.io) lists the embed and rerank models as their own components, embed-v4.0, the v3 embed models, rerank-v4.0-pro, rerank-v4.0-fast, rerank-v3.5 and the v3 rerank models (20). Embed 5 (30 September) and Rerank 5 (21 October) still aren't components on 1 November. The incident record for the 90 days to 1 November holds one API incident. On 1 September 2026, from 15:41 to 19:47 UTC, the embeddings endpoint, embed-v4.0, rerank-v4.0-fast and rerank-english-v3.0 ran with degraded performance during a Google Cloud outage, rated minor. The docs incident of 5 August doesn't touch the API, and nothing has been posted since 1 September, so minor incidents only (20). Published limits, embed 2,000 text inputs a minute on trial and production keys, image inputs 5 a minute on trial and 400 on production, rerank 10 requests a minute on trial and 1,000 on production, 1,000 calls a month on trial keys (15). The errors page documents 429 with example messages that say to wait and try again later, but gives no Retry-After header, backoff timing or retry guidance for 500s, which it sends to support (8 of 15). No SLA found for any self-serve tier (0). Embed 5 and Rerank 5 are generally available on the Cohere API per the changelog (10).

Gemini Embedding 45

Graded on the Developer API, which the listing's endpoint, docs and status link name. AI Studio has a status page for the Gemini API, but it renders in the browser and we couldn't read its components or history on 1 November, so 10 of 20 for the page and 5 of 30 for the incident line with no readable record, as the Gemini API and Gemini Live listings read the same page (10 and 5). Google Cloud's service health dashboard lists Vertex Gemini API and Vertex AI products but no Developer API product, so its history doesn't cover this endpoint. For the record, its incident feed has four incidents since 3 August (20 August, 1 September in us-central1-b, 8 and 9 October for Cloud Storage in us-central1, 20 October in europe-west2) and none names a Vertex AI or Gemini product. The 1 October note gave 20 for the two pages together and 15 of 30 as half credit between clean and unreadable, a reading the checklist doesn't have and the other Developer API listings don't use. No published rate limits for the embedding models. The docs send you to the AI Studio dashboard and print only the batch queue limits, 500,000 enqueued tokens at tier 1, re-read on 1 November (5 of 15). The troubleshooting page, re-read on 1 November, gives exponential backoff with jitter, retries 429, 408 and 5xx and not 400, 402 or 403, and says the official SDKs retry with backoff by default (15). Google's Gemini SLA on Vertex AI covers only the generateContent and streamGenerateContent methods, and the Vertex AI SLA lists training and custom prediction, so nothing covers embedContent, per the 1 October check, not re-read on 1 November (0). gemini-embedding-2 is Stable in the guide's model table and the deprecations table (10).

Maintenance & community Cohere Embed and Rerank +15

Cohere Embed and Rerank 90

Rerank 5 Pro and Fast shipped on 21 October 2026, after Embed 5 on 30 September (30). Four dated changelog entries in the 90 days to 1 November, north-small-translate (27 August), parse (9 September), embed-v5 (30 September) and rerank-v5 (21 October), and the Python SDK tagged 7.1.0 (26 August) and 7.2.0 and 7.3.0 (21 October) (20). cohere-python had 4 open issues and 20 open pull requests on 1 October. The embed bug opened on 15 August 2026 (batched embeddings dropped types absent from the first response) was fixed by pull request #797 on 20 October and released in 7.3.0, but issue reply times weren't re-read on 1 November, so the line stays (15 of 25). Official SDKs in four languages, cohere-python 7.3.0 tagged on 21 October 2026 with Rerank 5's relevant_spans types (15). CI in .github/workflows/ci.yml, and the 27 October commit fixes async headers ahead of the next regeneration (10).

Gemini Embedding 75

No new embedding model since gemini-embedding-2 went GA on 22 April 2026 per the changelog, 193 days ago. The newest dated change to the embedding models is google-genai 2.12.0 of 15 July 2026, which fills per-modality prompt token counts in gemini-embedding-2 responses, 109 days ago, so the line stays within 180 days (10). 16 dated changelog entries in the 90 days from 3 August 2026, the newest on 30 October (20). python-genai had 190 open issues and 103 open pull requests on 1 October, and every one of the newest twelve open issues carried a priority and type label, per the 1 October check, not re-read on 1 November (20 of 25). Current official SDKs, google-genai 2.34.0 tagged on 29 October 2026, with weekly tags through October, and @google/genai (15). mypy, docs and import workflows in the SDK repository, and Python 3.11 to 3.15 supported since 2.34.0 dropped 3.10 (10).

Security & auth Gemini Embedding +5

Cohere Embed and Rerank 55

Trial and production API keys, revocable from the dashboard, with no scopes or expiry that we found (20). The same key reaches datasets, fine-tuning, connectors and embed jobs, which include delete operations, with no way to limit it to embed and rerank (10 of 20). Returns vectors and scores, and rerank returns the caller's own documents (10). No per-key log or audit trail found in the docs we read (0 of 15). The Trust Center lists SOC 2 Type II, ISO 27001 and ISO 42001, API penetration test reports on request, and a downloadable Responsible Disclosure Policy for the bug bounty, but cohere.com/.well-known/security.txt still returns 404 on 1 November and no public advisories were found (15 of 20).

Gemini Embedding 60

Keys live in a Google Cloud project and can be restricted to the Gemini API and to IPs, referrers or apps, and the docs give a rotate-then-disable routine for leaks, per the 1 October check. No permission scopes below the API on the Developer API route, while Vertex AI uses OAuth with IAM (25), less 10 because the Discovery document (revision 20261101) lists access_token, oauth_token and key as query parameters, Google's OAuth 2.0 web-server guide documents sending a token as an access_token query parameter, and on 1 November an embedContent request with no credential answered 403 'Method doesn't allow unregistered callers' while one with a made-up ?access_token= answered 401 'Request had invalid authentication credentials'. So the API reads a token from the URL, the deduction Google APIs took on 17 October and 1 November (15 of 30). A key restricted to the Gemini API still reaches files, caches and tuned models, so least privilege below that needs Vertex IAM roles (15 of 20). Returns vectors only (10). Opt-in request logs in AI Studio for billed projects, per the Gemini API listing's check, and Cloud Audit Logs on Vertex AI (15). security.txt on google.com is valid to 2030-04-01 and points to the vulnerability reward programme, re-read on 1 November, and we didn't confirm a certification that names the Developer API, the reading the Gemini API listing takes (5 of 20).

Score by category

CategoryWeightCohere Embed and RerankGemini EmbeddingEdge
Reliability16%7345Cohere Embed and Rerank +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9289Cohere Embed and Rerank +3
Agent ergonomics13%8786Cohere Embed and Rerank +1
Security & auth14%5560Gemini Embedding +5
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9075Cohere Embed and Rerank +15
Transparency & trust7%7275Gemini Embedding +3
Negative events≤1500
TotalBB 75/100B 68.6/100

Facts side by side

FactCohere Embed and RerankGemini Embedding
KindHTTP APIHTTP API
VendorCohereGoogle
Hosted endpointhttps://api.cohere.com/v2/embedhttps://generativelanguage.googleapis.com/v1beta/models/gemini-embedding-2:embedContent
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
Price for text embeddingsnot published$0.10 per 1M tokens
x402nono
LicenceMIT (SDK)Apache-2.0 (SDK)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-04-22
Terms last updated2022-09-072026-04-28
Privacy policy last updated2026-05-012026-10-01
Customer content may train modelsyesyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity400 stars, 556k npm/wk, 2.6M PyPI/wk4k stars
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Cohere Embed and Rerank 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

Cohere Embed and Rerank

Embed 5 Pro and Fast share one embedding space with 128K context, and Rerank 5 adds passage-level Context Focus at public per-token prices. Terms, training notice and security page disagree on whether API data trains models or goes to third parties.

Gemini Embedding

Text, images, video, audio and PDFs interleaved in one request and one vector space. $0.20 per million text tokens, against $0.02 for OpenAI's small model.

Before you call either

Cohere Embed and Rerank

  1. Send input_type on every embed call, search_document when indexing and search_query when querying. The endpoint rejects a call without it
  2. Batch 96 inputs a call, the maximum, and stay under 2,000 inputs a minute. Use cohere-python 7.3.0 or later, which keeps every embedding type across batches
  3. Check billed_units in each rerank response. The pricing page lists Rerank 5 per million tokens while the FAQ still defines billing by searches
  4. Set max_tokens_per_doc on rerank. The default of 4,096 truncates long documents even on the 32K models
  5. Enable relevant_spans on Rerank 5 to pass only the matching passages to the model, and index with embed-v5.0-pro and query with embed-v5.0-fast at the same output_dimension

Gemini Embedding

  1. Don't send task_type to gemini-embedding-2. Prefix the text instead, task: search result | query: ... for queries and title: ... | text: ... for documents
  2. Ask for output_dimensionality 768 unless you need 3072. Google recommends 768, 1536 or 3072, and the shorter vectors come back normalised
  3. Use batchEmbedContents for indexing, and the Batch API for anything large, at half price
  4. Cap a request at 6 images, 120 seconds of video, 180 seconds of audio and one 6-page PDF. Split longer media first
  5. Don't mix vectors from gemini-embedding-001 and gemini-embedding-2 in one index
  6. Send the key in the x-goog-api-key header, never as a key or access_token query parameter, which the API also reads and which ends up in logs

Questions

Which is better for AI agents, Cohere Embed and Rerank or Gemini Embedding?

Cohere Embed and Rerank scores 75 (BB) on agent readiness against Gemini Embedding's 68.6 (B), and leads in 4 of 7 scored categories. Gemini Embedding leads on security & auth.

Do Cohere Embed and Rerank and Gemini Embedding need an API key?

Both need an API key.

Can an agent call Cohere Embed and Rerank and Gemini Embedding without installing anything?

Yes. Cohere Embed and Rerank has a hosted endpoint at https://api.cohere.com/v2/embed and Gemini Embedding at https://generativelanguage.googleapis.com/v1beta/models/gemini-embedding-2:embedContent.

Other comparisons with Cohere Embed and Rerank or Gemini Embedding

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.