Voyage Code 2 creates numerical embeddings for source code and related text. It is designed for semantic code retrieval, where a developer describes behavior or supplies a code fragment and the search system finds relevant implementations. The maker’s examples cover natural-language questions, code snippets and combinations of the two as search inputs.
Use it to build a repository search experience around actual development questions. A developer might look for the routine that removes only the first and last matching characters, or for the part of a project that applies a particular tree traversal. Prepare queries that express the behavior precisely, including the condition that distinguishes the intended implementation from a nearby but incorrect one.
Index code in useful units rather than splitting every file at an arbitrary character count. Keep a function signature, body and relevant explanation together. When a helper depends on local types or constants, retain enough surrounding text to make its purpose understandable. Store file paths, repository revisions and source locations outside the embedding so the result can open the original code directly.
This edition has a 16,000-token context window and produces 1,536-dimensional embeddings. Size the vector index for this representation and keep query and document embeddings associated with the same model. A collection already indexed with Voyage Code 2 can retain a consistent retrieval representation while its source records are updated. A move to another embedding edition should be treated as an index migration with an explicit comparison on the same repository.
For a natural-language query, describe the operation, inputs and relevant outcome. For a code query, include the fragment whose logic needs to be matched and explain any condition that matters to the search. A search for retry handling, for example, can specify whether the relevant code retries after a timeout or after a complete error response. The retrieved source should be checked for that distinction before it is used in an edit.
Keep documentation and source code traceable when both are indexed. An explanatory passage may be helpful context, while the implementation is the artifact a developer needs to inspect. Label these record types so a search page can show the correct destination and a coding assistant can distinguish a description from executable source.
Use the retrieved passages as context for repository navigation, implementation discovery or a coding assistant’s next step. Preserve the complete relevant snippet and its location when passing it onward. Similarity helps find candidate code; reviewing the actual inputs, side effects and contracts determines whether the candidate solves the current problem.
Evaluate retrieval on a set of real questions with known source answers. Include renamed functions, misleading comments, similar utilities with different edge cases and queries that use vocabulary absent from the code. Check whether the expected implementation appears among the useful results and whether the displayed snippet gives enough context to assess it. Retain those questions as the repository grows so changes to extraction, passage boundaries or indexing can be compared against the same tasks.
", "aboutText": "Voyage Code 2 creates numerical embeddings for source code and related text. It is designed for semantic code retrieval, where a developer describes behavior or supplies a code fragment and the search system finds relevant implementations. The maker’s examples cover natural-language questions, code snippets and combinations of the two as search inputs.\n\nUse it to build a repository search experience around actual development questions. A developer might look for the routine that removes only the first and last matching characters, or for the part of a project that applies a particular tree traversal. Prepare queries that express the behavior precisely, including the condition that distinguishes the intended implementation from a nearby but incorrect one.\n\nIndex code in useful units rather than splitting every file at an arbitrary character count. Keep a function signature, body and relevant explanation together. When a helper depends on local types or constants, retain enough surrounding text to make its purpose understandable. Store file paths, repository revisions and source locations outside the embedding so the result can open the original code directly.\n\nThis edition has a 16,000-token context window and produces 1,536-dimensional embeddings. Size the vector index for this representation and keep query and document embeddings associated with the same model. A collection already indexed with Voyage Code 2 can retain a consistent retrieval representation while its source records are updated. A move to another embedding edition should be treated as an index migration with an explicit comparison on the same repository.\n\nFor a natural-language query, describe the operation, inputs and relevant outcome. For a code query, include the fragment whose logic needs to be matched and explain any condition that matters to the search. A search for retry handling, for example, can specify whether the relevant code retries after a timeout or after a complete error response. The retrieved source should be checked for that distinction before it is used in an edit.\n\nKeep documentation and source code traceable when both are indexed. An explanatory passage may be helpful context, while the implementation is the artifact a developer needs to inspect. Label these record types so a search page can show the correct destination and a coding assistant can distinguish a description from executable source.\n\nUse the retrieved passages as context for repository navigation, implementation discovery or a coding assistant’s next step. Preserve the complete relevant snippet and its location when passing it onward. Similarity helps find candidate code; reviewing the actual inputs, side effects and contracts determines whether the candidate solves the current problem.\n\nEvaluate retrieval on a set of real questions with known source answers. Include renamed functions, misleading comments, similar utilities with different edge cases and queries that use vocabulary absent from the code. Check whether the expected implementation appears among the useful results and whether the displayed snippet gives enough context to assess it. Retain those questions as the repository grows so changes to extraction, passage boundaries or indexing can be compared against the same tasks.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "9065e8a252806fa8684df6d0696f370b10bc9eb9d15d7ee345837b5fac01042f", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "voyage-code-2Voyage Code 2 embeds source code and related text for semantic repository search. Natural-language questions, code snippets or combined queries can retrieve relevant implementations; this edition uses a 16,000-token context window and 1,536-dimensional vectors.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Voyage Code 2 creates numerical embeddings for source code and related text. It is designed for semantic code retrieval, where a developer describes behavior or supplies a code fragment and the search system finds relevant implementations. The maker’s examples cover natural-language questions, code snippets and combinations of the two as search inputs.
Use it to build a repository search experience around actual development questions. A developer might look for the routine that removes only the first and last matching characters, or for the part of a project that applies a particular tree traversal. Prepare queries that express the behavior precisely, including the condition that distinguishes the intended implementation from a nearby but incorrect one.
Index code in useful units rather than splitting every file at an arbitrary character count. Keep a function signature, body and relevant explanation together. When a helper depends on local types or constants, retain enough surrounding text to make its purpose understandable. Store file paths, repository revisions and source locations outside the embedding so the result can open the original code directly.
This edition has a 16,000-token context window and produces 1,536-dimensional embeddings. Size the vector index for this representation and keep query and document embeddings associated with the same model. A collection already indexed with Voyage Code 2 can retain a consistent retrieval representation while its source records are updated. A move to another embedding edition should be treated as an index migration with an explicit comparison on the same repository.
For a natural-language query, describe the operation, inputs and relevant outcome. For a code query, include the fragment whose logic needs to be matched and explain any condition that matters to the search. A search for retry handling, for example, can specify whether the relevant code retries after a timeout or after a complete error response. The retrieved source should be checked for that distinction before it is used in an edit.
Keep documentation and source code traceable when both are indexed. An explanatory passage may be helpful context, while the implementation is the artifact a developer needs to inspect. Label these record types so a search page can show the correct destination and a coding assistant can distinguish a description from executable source.
Use the retrieved passages as context for repository navigation, implementation discovery or a coding assistant’s next step. Preserve the complete relevant snippet and its location when passing it onward. Similarity helps find candidate code; reviewing the actual inputs, side effects and contracts determines whether the candidate solves the current problem.
Evaluate retrieval on a set of real questions with known source answers. Include renamed functions, misleading comments, similar utilities with different edge cases and queries that use vocabulary absent from the code. Check whether the expected implementation appears among the useful results and whether the displayed snippet gives enough context to assess it. Retain those questions as the repository grows so changes to extraction, passage boundaries or indexing can be compared against the same tasks.
POST /v1/embeddingstextembedding| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits voyage-code-2 Conditions: Use the exact Ailoot model selector. | Default— |
Fieldinput | Typestring or array<string> | RequirementRequired | Values & limits Conditions: A text or list of texts; keep one vector for every returned data item and its index. | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, input |
Parameteroptional | Contract |
Parametermaterial_types | Contracttext |
Parameterconditions | ContractSend text with the selected model; retain every returned vector and its index. |
Lifecycle: synchronous
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0.0004 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\ncat > request.json <<'JSON'\n{\n "model": "voyage-code-2",\n "input": "The quick brown fox jumps over the lazy dog"\n}\nJSON\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/embeddings \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o embeddings.json\n# Keep every data item and its index, the full usage object and response headers.\nAiloot Ultra voyage-code-2
Use the method paths shown above.