Validate that Voyage 4 models share an embedding space, then connect that result to asymmetric retrieval and concrete cost savings.
• A valid VOYAGE_API_KEY is set in the environment.
See the exact VAI command, the matching Voyage AI layer, and the MongoDB query shape behind the demo.
vai benchmark space
The benchmark proves that multiple Voyage 4 models can represent the same text in a compatible space. The estimate command in the tape then turns that abstract property into an operational cost argument.
Share or copy this demo
Keep it lightweight. The prepared text stays behind the buttons.
Share
Copy
LinkedIn opens the share dialog and copies the prepared text so you can paste it in quickly.
The full walkthrough is included here so anyone can replay the demo exactly as published.
More shareable workflows from the same VAI demo library.
Survey the Voyage model lineup, explain benchmark context, and then measure embedding latency on your own hardware before choosing a production model.
VAI command
vai benchmark embed --input 'What is the best way to index a large document corpus?'
Show Under the Hood
Prerequisites
A valid VOYAGE_API_KEY is set in the environment.
Start from first principles: generate a Voyage embedding, inspect its shape, and compare full-size versus Matryoshka-reduced vectors.
VAI command
vai embed 'MongoDB Atlas makes vector search production-ready'
Show Under the Hood
Prerequisites
A valid VOYAGE_API_KEY is set in the environment.
