Retrieval embeddings and reranking
How to use
Voyage AI.
Creating high-quality text or multimodal embeddings and reranking candidate results for semantic search, RAG, code search, and domain-specific retrieval.
Voyage AI is a embedding and reranking platform for semantic search, retrieval-augmented generation, code and domain retrieval, and multimodal indexing. Creating high-quality text or multimodal embeddings and reranking candidate results for semantic search, RAG, code search, and domain-specific retrieval. This guide covers the whole path in one place: official access, a first session that produces something reviewable, the checks that make output trustworthy, and the permissions worth limiting before you connect real work.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Access & setup
Find, install, and sign in to Voyage AI
Get into the official Voyage AI experience with the right account and a setup you understand.
- 01
Start at https://www.voyageai.com/ and confirm the domain before entering account or payment information.
- 02
Availability: Voyage AI is accessed through its web dashboard, hosted REST APIs, Python and TypeScript clients, and supported private deployment options including MongoDB listings in Azure.
- 03
A Voyage account and API key, server-side secret storage, an owned and permissioned corpus, a vector index, labeled retrieval evaluations, token and rate budgets, approved data handling, monitoring, and a reindex and rollback plan.
- 04
Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.
- 05
Run one low-risk test task before connecting sensitive files, repositories, or workspace data.
- Use official download pages.
- Review permissions during setup.
- Keep installers and applications updated.
First session
Your first useful Voyage AI session
Learn the interaction loop using a small task with a clear outcome.
- 01
Define the search users, corpus owners, permissions, languages and modalities, relevance labels, freshness, latency, throughput, storage, data handling, cost, and deletion requirements.
- 02
Create a server-side API key, choose a current embedding model by measured task fit, set input_type to document for the corpus and query for searches, and record model, dimension, datatype, tokenizer, and truncation choices.
- 03
Index a small versioned corpus with stable IDs and metadata, retrieve candidates on labeled queries, then test whether a current reranker improves ranking enough to justify its latency and cost.
- 04
Measure recall, ranking quality, no-answer behavior, permissions, multilingual and adversarial cases, latency, errors, and spend before canarying, monitoring drift, and preserving the prior index for rollback.
- State the outcome before the background.
- Provide the real source material.
- Review the result before expanding the task.
Quality control
Check the quality of Voyage AI output
Turn generated code into a change you would put your name on in review.
- 01
Restate the intended behaviour and the acceptance criteria before reading a single generated line.
- 02
Read the diff rather than the chat summary; the summary describes intent, the diff describes what actually changed.
- 03
Run the test suite, then write a test that would fail if the change were wrong, and confirm it passes for the right reason.
- 04
Check the edges the model tends to skip: error paths, null and empty cases, concurrency, and migration or rollback behaviour.
- 05
Trace every new dependency, network call, and file write, and confirm each one is genuinely required.
- Review the diff, never the description of the diff.
- A passing test suite proves the tests pass, not that the change is correct.
- Keep changes small enough that a human can actually review them.
Privacy & permissions
Use Voyage AI safely
Give the tool enough repository access to help, and no more than that.
- 01
Decide what the tool may read and what it may write before connecting a repository.
- 02
Scope tokens and integrations to the narrowest repository, branch, and permission set that still works.
- 03
Keep secrets out of the context window: use environment variables and secret stores, never inline credentials.
- 04
Require review before generated code touches authentication, payments, permissions, migrations, or deletion paths.
- 05
Audit what the integration retained after the session, and revoke access that is no longer needed.
- Embedding compatibility, dimensions, tokenizers, limits, and recommended models change; automatic truncation can silently remove decisive content, and relevance scores are not truth or permission checks. Voyage says hosted-API customers can opt out of storage and training use for zero-day retention through an organization-admin control. Keep keys server-side, confirm current data settings, preserve source permissions and deletion, separate query and document inputs, version every vector with its model configuration, evaluate reranking on labeled data, and reindex deliberately when compatibility changes.
- Follow your organisation's approved-use policy.
- Never treat fluent output as authorization to act.
Core workflows
Step-by-step ways to use Voyage AI for the work it does best.
Each workflow is a separate guide with its own steps and review checkpoints.
Create embeddings from permissioned source material with stable identities, explicit model semantics, reproducible chunking, and deletion lineage.
↗ 02 WorkflowEvaluate Voyage retrieval and rerankingMeasure candidate recall and final ranking separately so a polished reranker result cannot hide missing evidence, silent truncation, or permission leakage.
↗Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this guide.
- Voyage AI introduction ↗
- Voyage AI quickstart tutorial ↗
- Voyage text embeddings ↗
- Voyage rerankers ↗
- Voyage data policy FAQ ↗