Embedding Models
Introduction
Text embedding models transform text into dense vector representations that power semantic search, dense retrieval, retrieval-augmented generation (RAG), and classification tasks. NeMo AutoModel includes custom bidirectional backbones and configures supported Hugging Face AutoModel backbones with non-causal attention for retrieval training.
For cross-encoder pairwise scoring, see Reranking Models.
Embedding models use bi-encoders to produce dense representations for queries and documents independently. They are the standard path for embedding generation and first-stage dense retrieval.
Optimized Backbones (Bidirectional Attention)
The stock ministral3 path is preferred. The ministral3_bidirec model type remains available for compatibility with legacy checkpoints and resolves to the custom Ministral3BidirectionalModel.
Hugging Face Auto Backbones
Any Hugging Face model that can be loaded with AutoModel can be used as an embedding backbone. The fallback path sets config.is_causal: false; verify that an unregistered architecture honors this flag before using it for retrieval training.
Example Recipes
Supported Models
This table combines recipe-backed checkpoints with documented model families. Dates show when the current checkpoint first appeared in a recipe, or when a documentation-only family page was added. See the combined model support log for recipe-backed checkpoints of every model type.
Supported Workflows
- Fine-tuning (Bi-Encoder): Contrastive learning on query-document pairs to produce embedding models
- LoRA/PEFT: Parameter-efficient fine-tuning for embedding backbones
- ONNX Export: Export trained embedding models for deployment (case by case, model dependent)
Dataset
Retrieval fine-tuning requires query-document pairs: each example is a query paired with one positive document and one or more negative documents. Both inline JSONL and corpus ID-based JSON formats are supported. See the Retrieval Dataset guide.