Nvidia Nv Embed V1 is listed in the o10 fulfillment catalog as of 2026-06-27. Openrouter publishes this model without a published context window in this snapshot. o10 lists Nvidia Nv Embed V1 on NVIDIA NIM at routing band C0. API slug nvidia-nv-embed-v1. Verify list prices against the venue you call.

Last updated: 2026-06-27. Full catalog. Reference prices are dated snapshots. Compare total cost and measured task quality before choosing a route.

Nvidia Nv Embed V1. Specs, hosts, and routing

AnswersSelf-contained

What is Nvidia Nv Embed V1?

Nvidia Nv Embed V1 is a embedding model from openrouter (slug: nvidia-nv-embed-v1). Pick Nvidia Nv Embed V1 when your evals pass at band C0 and the fulfillment hosts below are allowed venues.

Catalog snapshot 2026-06-27.

When should you pick Nvidia Nv Embed V1?

Pick Nvidia Nv Embed V1 when your evals pass at band C0 and the fulfillment hosts below are allowed venues. Nvidia Nv Embed V1 is the openrouter SKU in this catalog. Compare same-provider siblings before jumping labs.

How does Nvidia Nv Embed V1 differ from sibling models?

Nvidia Nv Embed V1 is the openrouter SKU in this catalog. Compare same-provider siblings before jumping labs.

How much does Nvidia Nv Embed V1 cost per million tokens?

Nvidia Nv Embed V1 does not have published per-token pricing in the current gateway snapshot. See fulfillment hosts below for routing options.

Pricing unavailable in current snapshot.

Where can you run Nvidia Nv Embed V1?

Nvidia Nv Embed V1 is configured on NVIDIA NIM. Known host IDs: nvidia_nim: nvidia_nim/nvidia/nv-embed-v1. This model is cataloged but not marked routable for chat routing.

What is Nvidia Nv Embed V1's context window?

Nvidia Nv Embed V1 context limits depend on the fulfillment host. Check the specifications table for endpoint-specific limits.

What o10 routing band is Nvidia Nv Embed V1?

Nvidia Nv Embed V1 is classified at o10 routing band C0. Bands group models by cost tier and eval profile: C0 (economy), C1 (standard), C2 (capable), C3/C4 (frontier). Chat routing is disabled for this slug.

Who makes Nvidia Nv Embed V1?

Nvidia Nv Embed V1 is attributed to source provider openrouter in the o10 catalog. Fulfillment hosts (NVIDIA NIM) supply API access; list pricing may differ by venue.

01Deep dive

Specifications

Nvidia Nv Embed V1 in the o10 unified catalog.

Nvidia Nv Embed V1 specifications
FieldValue
o10 slug`nvidia-nv-embed-v1`
Typeembedding
BandC0
RoutableNo
Source provideropenrouter
Primary hostNVIDIA NIM
02Deep dive

Fulfillment hosts

Upstream venues configured for Nvidia Nv Embed V1.

Nvidia Nv Embed V1 fulfillment routes
HostUpstream model ID
nvidia_nimnvidia_nim/nvidia/nv-embed-v1
03Deep dive

Routing with o10

Eval-gated model selection for this slug.

o10 slug: nvidia-nv-embed-v1. Band: C0. Routable: no.

See [/models/routing](/models/routing) for smart aliases (o10/auto, o10/frontier, o10/squad) and [/kyi](/kyi) for governance.

SourceMethodology

Fulfillment catalog 2026-06-27. Gateway pricing joined where slug match exists.

FAQFrequently asked questions

Common questions

How much does Nvidia Nv Embed V1 cost?

Nvidia Nv Embed V1 has no published per-token price in the current gateway snapshot. Use the fulfillment hosts table to identify available venues.

What is Nvidia Nv Embed V1's context window?

Context limits for Nvidia Nv Embed V1 vary by fulfillment host. See the specifications table on this page.

Which hosts serve Nvidia Nv Embed V1?

Nvidia Nv Embed V1 (nvidia-nv-embed-v1) is configured on: NVIDIA NIM. Upstream model IDs are listed in the fulfillment routes section.

Is Nvidia Nv Embed V1 routable through o10?

No. Nvidia Nv Embed V1 is cataloged but not enabled for chat routing in the current fulfillment config.

How do I call Nvidia Nv Embed V1 via o10?

Use o10 slug "nvidia-nv-embed-v1" in the model field. See /models/routing for smart aliases (o10/auto, o10/frontier, o10/squad).

How does o10 route this model?

o10 routes Nvidia Nv Embed V1 only when per-use-case evals clear at your quality floor. Band C0 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.