Voyage 3 Large is a text embedding model for finding relevant information across a collection of documents. It represents each supplied text as a numerical vector, allowing an application to compare a search request with passages whose wording may be different but whose meaning is related. Voyage AI positions this edition for general-purpose and multilingual retrieval, covering material such as technical documentation, conversations and long documents.
Build the searchable collection from the information people actually need to recover. For a product knowledge base, keep the explanation of a feature together with its prerequisites and relevant exceptions. For meeting records, preserve speaker labels and enough surrounding discussion to make the topic understandable. Split a large source at useful boundaries and retain the source title, document identifier and passage position alongside each vector.
Prepare a search question as a query and indexed material as documents. In the maker’s text-embedding workflow, the input type gives the model the retrieval role of the text. A query such as “How can a member recover access after losing a security key?” can then be compared with support passages describing the recovery procedure, even if those passages use different phrasing. Keep the original passage available so the search result can show the evidence behind its match.
The model has a 32,000-token context window. A long input can preserve a complete section, but a whole document is not always the most useful search unit. A broad vector may point to the right file while leaving the reader to find the precise answer. Choose passage boundaries around the result you want to display, and keep headings, qualifications and definitions with the content they explain.
Voyage 3 Large supports vectors with 2,048, 1,024, 512 or 256 dimensions. The maker also documents floating-point, signed or unsigned eight-bit, and binary representations. These choices let a retrieval system compare vector detail with index size and search behavior. Select the format supported by the intended vector store, then evaluate it on the actual corpus and representative questions before choosing the production index settings.
For multilingual search, include test questions in the languages your users use and review the retrieved source passages in their original language. A shared search interface can serve several language collections, while document metadata still identifies the source locale and version. Preserve meaningful names, abbreviations and domain terms during extraction rather than replacing them with a generic summary before embedding.
Use the vectors to retrieve candidate passages for a search page, knowledge assistant or document-selection step. Keep the same model and vector settings for the indexed collection and its queries. When replacing an embedding model or changing vector dimensions, rebuild and compare the affected index deliberately; a vector’s length alone does not identify how it was produced.
Judge the result by useful retrieval: whether the correct passage appears, whether nearby but misleading passages rank above it, and whether the displayed excerpt contains the answer. Keep a small set of real questions with expected sources, including ambiguous wording and near-duplicate documents. The embedding provides a searchable representation; the application retains the source text, permissions and links needed to turn a match into a usable result.
", "aboutText": "Voyage 3 Large is a text embedding model for finding relevant information across a collection of documents. It represents each supplied text as a numerical vector, allowing an application to compare a search request with passages whose wording may be different but whose meaning is related. Voyage AI positions this edition for general-purpose and multilingual retrieval, covering material such as technical documentation, conversations and long documents.\n\nBuild the searchable collection from the information people actually need to recover. For a product knowledge base, keep the explanation of a feature together with its prerequisites and relevant exceptions. For meeting records, preserve speaker labels and enough surrounding discussion to make the topic understandable. Split a large source at useful boundaries and retain the source title, document identifier and passage position alongside each vector.\n\nPrepare a search question as a query and indexed material as documents. In the maker’s text-embedding workflow, the input type gives the model the retrieval role of the text. A query such as “How can a member recover access after losing a security key?” can then be compared with support passages describing the recovery procedure, even if those passages use different phrasing. Keep the original passage available so the search result can show the evidence behind its match.\n\nThe model has a 32,000-token context window. A long input can preserve a complete section, but a whole document is not always the most useful search unit. A broad vector may point to the right file while leaving the reader to find the precise answer. Choose passage boundaries around the result you want to display, and keep headings, qualifications and definitions with the content they explain.\n\nVoyage 3 Large supports vectors with 2,048, 1,024, 512 or 256 dimensions. The maker also documents floating-point, signed or unsigned eight-bit, and binary representations. These choices let a retrieval system compare vector detail with index size and search behavior. Select the format supported by the intended vector store, then evaluate it on the actual corpus and representative questions before choosing the production index settings.\n\nFor multilingual search, include test questions in the languages your users use and review the retrieved source passages in their original language. A shared search interface can serve several language collections, while document metadata still identifies the source locale and version. Preserve meaningful names, abbreviations and domain terms during extraction rather than replacing them with a generic summary before embedding.\n\nUse the vectors to retrieve candidate passages for a search page, knowledge assistant or document-selection step. Keep the same model and vector settings for the indexed collection and its queries. When replacing an embedding model or changing vector dimensions, rebuild and compare the affected index deliberately; a vector’s length alone does not identify how it was produced.\n\nJudge the result by useful retrieval: whether the correct passage appears, whether nearby but misleading passages rank above it, and whether the displayed excerpt contains the answer. Keep a small set of real questions with expected sources, including ambiguous wording and near-duplicate documents. The embedding provides a searchable representation; the application retains the source text, permissions and links needed to turn a match into a usable result.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "fc754b505f99f890d39f0e17e2640d86f74c9a1717bb0982c45b2efc37313258", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "voyage-3-largeVoyage 3 Large turns text into vectors for general-purpose and multilingual retrieval. Its 32,000-token input window, selectable vector dimensions and quantized formats support searchable knowledge bases, document discovery and retrieval-augmented generation.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Voyage 3 Large is a text embedding model for finding relevant information across a collection of documents. It represents each supplied text as a numerical vector, allowing an application to compare a search request with passages whose wording may be different but whose meaning is related. Voyage AI positions this edition for general-purpose and multilingual retrieval, covering material such as technical documentation, conversations and long documents.
Build the searchable collection from the information people actually need to recover. For a product knowledge base, keep the explanation of a feature together with its prerequisites and relevant exceptions. For meeting records, preserve speaker labels and enough surrounding discussion to make the topic understandable. Split a large source at useful boundaries and retain the source title, document identifier and passage position alongside each vector.
Prepare a search question as a query and indexed material as documents. In the maker’s text-embedding workflow, the input type gives the model the retrieval role of the text. A query such as “How can a member recover access after losing a security key?” can then be compared with support passages describing the recovery procedure, even if those passages use different phrasing. Keep the original passage available so the search result can show the evidence behind its match.
The model has a 32,000-token context window. A long input can preserve a complete section, but a whole document is not always the most useful search unit. A broad vector may point to the right file while leaving the reader to find the precise answer. Choose passage boundaries around the result you want to display, and keep headings, qualifications and definitions with the content they explain.
Voyage 3 Large supports vectors with 2,048, 1,024, 512 or 256 dimensions. The maker also documents floating-point, signed or unsigned eight-bit, and binary representations. These choices let a retrieval system compare vector detail with index size and search behavior. Select the format supported by the intended vector store, then evaluate it on the actual corpus and representative questions before choosing the production index settings.
For multilingual search, include test questions in the languages your users use and review the retrieved source passages in their original language. A shared search interface can serve several language collections, while document metadata still identifies the source locale and version. Preserve meaningful names, abbreviations and domain terms during extraction rather than replacing them with a generic summary before embedding.
Use the vectors to retrieve candidate passages for a search page, knowledge assistant or document-selection step. Keep the same model and vector settings for the indexed collection and its queries. When replacing an embedding model or changing vector dimensions, rebuild and compare the affected index deliberately; a vector’s length alone does not identify how it was produced.
Judge the result by useful retrieval: whether the correct passage appears, whether nearby but misleading passages rank above it, and whether the displayed excerpt contains the answer. Keep a small set of real questions with expected sources, including ambiguous wording and near-duplicate documents. The embedding provides a searchable representation; the application retains the source text, permissions and links needed to turn a match into a usable result.
POST /v1/embeddingstextembedding| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits voyage-3-large 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-3-large",\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-3-large
Use the method paths shown above.