[Models](/models)/nvidia/Nemotron-3-Embed-1B-BF16

NVIDIA Open Model License

# Nemotron-3-Embed-1B-BF16

by nvidia

The 1B sibling of Nemotron-3-Embed, for when 8B does not fit the budget

1.14Bparams

[HuggingFace](https://huggingface.co/nvidia/Nemotron-3-Embed-1B-BF16)[Run it on your own data, free](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=model_page&utm_campaign=mvs_onramp)

Identifiers

Model ID

`nvidia/Nemotron-3-Embed-1B-BF16`

## Deploy Nemotron-3-Embed-1B-BF16

Single-tenant

Mixpeek has no managed extractor for this model. On a single-tenant deployment you upload the weights and a custom plugin serves them next to the rest of your pipeline.

[Read the customer-hosted guide](https://mixpeek.com/docs/customer-hosted/overview) [Talk to us about single-tenant](/demo)

## Overview

Same family and same retrieval-first intent as the 8B, at roughly an eighth of the size. The tradeoff is the usual one: recall on hard queries against throughput and cost per million chunks.

The useful way to choose is to run both over your own corpus rather than a benchmark. A 1B model that answers your queries is worth more than an 8B that answers someone else's, and the gap between them narrows sharply on domains where the vocabulary is already unambiguous.

Packaged for sentence-transformers and vLLM, like its larger sibling.

## Architecture

Ministral3Model, 1,140,918,272 parameters, BF16 weights. Sentence-similarity pipeline packaged for sentence-transformers.

## Mixpeek SDK Integration

IngestRetrieve

// No extractor parameter takes a Hugging Face model id (checked against
// GET /v1/discovery/extractors, which returns 13), so Nemotron-3-Embed-1B-BF16 runs
// on your side and the output is upserted through POST
// /v1/namespaces/{namespace\_id}/documents/upsert. On Enterprise the other
// path is to upload the weights instead: POST /v1/namespaces/{id}/models
// accepts the huggingface format and a custom plugin loads them.
const res = await fetch(
  "https://api.mixpeek.com/v1/namespaces/ns\_your\_namespace/documents/upsert",
  {
    method: "POST",
    headers: {
      Authorization: "Bearer API\_KEY",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      collection\_id: "col\_your\_collection",
      documents: \[
        {
          document\_id: "asset-00412",
          // The vector name has to match a vector index on the collection.
          vectors: { "text-embedding": yourVector },
          payload: { source\_key: "archive/2026/asset-00412" },
        },
      \],
    }),
  },
);

// Managed alternative, if this exact model is not the requirement:
// text\_extractor@v1 runs intfloat/multilingual-e5-large-instruct
// (1024-d) over a bucket, with no inference of your own.

## Capabilities

*   Dense text embeddings for semantic search
*   Retrieval over document chunks for RAG
*   Cheap enough to run over a large corpus rather than a sample
*   A first-pass encoder ahead of a larger reranking stage

## Use Cases on Mixpeek

The text half of a multimodal index where budget rules out an 8B encoder

First-stage retrieval feeding a more expensive reranker

Corpora large enough that per-chunk cost dominates the decision

A baseline to measure whether the 8B is worth its extra cost on your data

## Explore on Mixpeek

[

Browse all models

Search the full model catalog

](/models)[

Feature Extractors

See how Mixpeek runs models as extractors

](/extractors)[

Mixpeek Vector Store

Store & search embeddings at scale

](/mvs)[

Pricing

Usage-based pricing for pipelines

](/pricing)[

All Curated Lists

Compare models, APIs & infrastructure

](/curated-lists)

### Specification

Organizationnvidia

Retriever\-

Parameters1.14B

LicenseNVIDIA Open Model License

Downloads/moN/A

### Build a pipeline with Nemotron-3-Embed-1B-BF16

Add this model to a processing pipeline alongside other extractors. Combine with retrieval stages for end-to-end search.

[Run it on your own data, free](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=model_page&utm_campaign=mvs_onramp)