Eleven Realtime Translation
Translate live speech into spoken audio in more than 90 languages through an enterprise WebSocket API.
Create multilingual embeddings for semantic search across document text, page images and combined image-text content.
Visit website
NVIDIA Nemotron 3.5 Embed 8B is an embedding model for multilingual semantic search and document retrieval. It accepts document text, page images or combined image-text inputs, producing vectors that can be matched against text queries.
The downloadable checkpoint is Nemotron-3.5-Embed-8B-BF16. Search engineers can obtain its weights from Hugging Face or access the model through NVIDIA NIM to build retrieval components for search and RAG applications.
Embed pages containing text, tables, charts and infographics, including combined image-text documents.
Text retrieval was evaluated across 34 languages and image retrieval across 18 languages. These counts describe evaluation coverage.
Generate normalized 4,096-dimensional vectors, or truncate and renormalize them for shorter representations such as 1,024 or 512 dimensions.
The checkpoint includes examples for Transformers, Sentence Transformers and vLLM.
NVIDIA provides a model endpoint and API reference for developers evaluating hosted embedding workflows.
Search engineers could retrieve relevant pages from reports containing charts, tables and prose.
Enterprise developers could build semantic search over document collections in multiple languages.
Application teams could supply relevant document passages or page images to a separate answer-generation system.
Model materials are available free of charge under OpenMDW-1.1, subject to its terms. NVIDIA also lists a free endpoint for evaluation. Compute, hosting and production services are separate considerations.
Check current pricing ↗Yes. NVIDIA permits commercial and non-commercial use under OpenMDW-1.1. Redistribution requires retaining the agreement and applicable notices.
Yes. Document-page inputs can contain charts, tables, infographics and text, retrieved using text queries.
A typical system stores document embeddings in a vector database linked to the original content. RAG applications also need a separate model to generate answers.