Niches · Embeddings & rerankers

Change or pin an embedding model without breaking the index

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
17companies, fit with a limit
114companies carry the tag
9share of the category's work
8first-hand accounts

What counts as done

The listing publishes dated model ids and a deprecation policy with a notice period, says which models share a vector space, and returns the same vector for the same input on a pinned id and runtime; where an open-weight copy exists the docs say it reproduces the hosted vectors.

Measured, for our own tests: cosine similarity of 0.999 or more between two calls on the same pinned id. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: our embedding model is being deprecated, what now, upgrade to the newer embedding model, will these vectors stay the same next year, move off this provider

Does the job, with a limit 18

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Nova Multimodal Embeddings BB
Amazon Web Services, Inc.
A versioned id (amazon.nova-2-multimodal-embeddings-v1:0) and a lifecycle policy (EOL no sooner than 28 October 2026, legacy period of at least 6 months), but nothing on shared vector spaces or whether a pinned id returns the same vector. source
Cohere Embed and Rerank BB
Cohere Inc.
A deprecation policy with email notice and dated retirements, and Pro and Fast share a space; ids are versioned (embed-v5.0-pro) but not dated, and nothing says a pinned id returns the same vector. source
EmbeddingGemma 2 B
Google LLC (RDAP registrant of gemma.ai; the card names Google DeepMind as author)
Open weights can be pinned by commit and kept indefinitely, which an account chose for that reason, but the card says nothing on reproducibility across runtimes, dtype or hardware, and nothing on sharing a space with EmbeddingGemma 300M. source
EmbeddingGemma 300M D
Google LLC (RDAP registrant of gemma.ai; the card names Google DeepMind as author)
Weights unchanged since 25 September 2025 and pinnable, but no statement on reproducibility across runtimes, quantised builds or hardware, or on any shared space with EmbeddingGemma 2. source
Gemini Embedding B
Google LLC
Release and shutdown dates per model (001 shuts 14 May 2028), advance-notice policy, and 001 and 2 are documented as incompatible spaces; ids are undated aliases and nothing says a pinned id returns the same vector. source
Granite Embedding Small English R2 E
International Business Machines Corporation
Open weights pinnable by commit, but no deprecation policy, no statement on reproducibility across runtimes, and the last assessment found model.safetensors replaced on 6 January 2026 without a note. source
Jina Embeddings and Reranker B
Jina AI GmbH
The catalogue lists model ids and creation dates, but no deprecation policy, notice period or changelog was found, and nothing says a pinned id returns the same vector. source
jina-embeddings-v5-omni-small D
Jina AI GmbH, a subsidiary of Elastic N.V. (per the jina-embeddings listing's 2 October 2026 check)
The card says vectors share a space with jina-embeddings-v5-text-small, so a text index extends without re-embedding, but nothing says local vectors reproduce the hosted API's or stay the same across vLLM and Transformers. source
Mistral Embed and Codestral Embed B
Mistral AI (RCS Paris 952 418 325)
Dated ids (mistral-embed-2312, codestral-embed-2505) and a deprecation table with deprecation and retirement dates, but no stated notice period, no shared-space note and nothing on vector stability. source
Nomic Embed E
Nomic, Inc.
The docs say local embeddings match the API's within a small margin of error, but there are no dated ids or deprecation policy, and the legacy reference warns endpoints may be removed. source
NVIDIA NeMo Retriever Embedding and Reranking NIMs B
NVIDIA Corporation
Model ids name the precision (BF16, NVFP4), but the default checkpoint changes by GPU, FP16 on some and NVFP4 on others, so a pinned container doesn't guarantee the same vectors; release notes are undated. source
OpenAI embeddings BB
OpenAI OpCo, LLC
A deprecation policy with at least 6 months' notice for generally available models and email to active users, but ids are undated, no shared space is stated, and an account saw text-embedding-3-small listed for deprecation and then removed without explanation. source
Qwen3-Embedding-0.6B B
Alibaba Cloud (the registrant of qwen.ai per RDAP, carried from the Qwen3.8-27B check)
Open weights pinnable by commit, but an account and an open issue found vectors differ between vLLM versions and GPU models, with only identical hardware and version reproducing them. source
Qwen3-Embedding-4B BB
Alibaba Cloud (named in the copyright line of the 8B sibling's Apache 2.0 licence; this repository has no LICENSE file)
Open weights pinnable by commit, but nothing in the card on reproducibility, and open issues report vectors differing across vLLM versions and across inference providers. source
Qwen3-Embedding-8B BB
Alibaba Cloud (named in the licence's copyright line)
Open weights pinnable by commit, but nothing in the card on reproducibility, and open issues report vectors differing across vLLM versions and across inference providers. source
Qwen3-VL-Embedding-2B C
Alibaba Cloud (RDAP names Alibaba Cloud (Singapore) Private Limited as the registrant of qwen.ai)
Open weights pinnable by commit, but an account and a second user found vectors from vLLM 0.14 didn't match the offline Transformers path, so a pinned model isn't enough. source
Qwen3-VL-Embedding-8B B
Alibaba Group (Tongyi Lab, named in the copyright line of the GitHub repository's Apache 2.0 licence)
Open weights pinnable by commit, but nothing on reproducibility; the 2B sibling's vLLM vectors didn't match the Transformers path in an account. source
Voyage AI embeddings and rerankers B
Voyage AI Innovations, Inc.
All 4-series models, including the open-weight nano, are documented as sharing a space, and older models stay accessible, but ids are undated, there is no deprecation policy with a notice period, and nothing on vector stability. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
ZeroEntropy zerank and zembed F
ZeroEntropy, Inc.
The hosted model was withdrawn and new signups closed, a named blocker; nothing says the open weights reproduce the hosted vectors, so an index built on the API needs re-embedding to be safe. source

What stops agents finishing

  • hosted model withdrawn with endpoints answering 503 (ZeroEntropy) or listed for deprecation
  • runtime or GPU change alters vectors, so a pinned model is not enough
  • re-embedding cost (weeks of GPU for 200M vectors) with no adapter or shared space

Around it

After: embeddings.bulk-backfill, vector-search.ingest-sync.

Where this comes from

Weight 9 of 100 in Embeddings & rerankers: 8 of 62 accounts (91 account-use-case tags, accounts counted in each use case they fit, scaled to 100 and rounded by hand); OpenAI deprecation scare, Jina emergency migration, CLIP to SigLIP re-embedding cost and vLLM drift; ZeroEntropy's shutdown is in the context file, not an account

The same as data: /api/v1/use-cases/embeddings.model-migration.json, or the MCP tool get_use_case with id embeddings.model-migration. Other jobs in this category: /api/v1/niches?category=embeddings.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.