Voyage 3.5 Lite converts text into embeddings for semantic retrieval. Voyage AI describes this edition as optimized for latency and cost, making it a candidate for search experiences that embed incoming questions frequently or maintain a large collection of searchable passages. The output is a numerical representation of the supplied text, which a retrieval application compares with vectors stored for its source material.
Start with a collection whose boundaries match the user’s task. For a help center, one passage might explain a procedure and its prerequisites. For a discussion archive, keep enough of a reply chain to identify what the response addresses. A result should lead to a readable piece of evidence, so store the original text, stable source link and document metadata with each embedding.
Write test queries as users would ask them. “Where do I change the address on an invoice?” is a more useful search check than copying the relevant article heading. Include short questions, paraphrases, domain abbreviations and cases that mention several concepts. Review the returned passages and identify whether a missed result comes from missing source content, poor passage boundaries or a retrieval choice.
The maker documents a 32,000-token context window. This capacity allows substantial text inputs, while passage length remains a design choice for the search experience. Keep a compact answer together with necessary conditions; avoid cutting a definition away from the term it explains. Extract readable text from the source and remove navigation repeated on every page when it obscures the information the user wants.
Voyage 3.5 Lite supports 2,048, 1,024, 512 and 256 dimensions. Floating-point, eight-bit integer and binary representations provide additional choices for the vector index. Test a smaller or quantized representation against the same questions and corpus used for the full-precision baseline. Record the selected model, dimension and data type with the index so query vectors use the corresponding settings.
In the maker’s retrieval workflow, identify indexed passages as documents and incoming searches as queries. Preserve the mapping from every returned vector to its input text when processing several passages together. A successful embedding operation supplies vectors; the application still needs to put them in the correct records and expose the source excerpt when a user opens a result.
Use this edition for a searchable support collection, a document-discovery tool or the retrieval stage of an assistant. For multilingual material, evaluate the language combinations present in your own collection rather than relying on a single English test. Keep permissions and locale metadata available to the application so a relevant match can be filtered and displayed in the right context.
For growing collections, update the vectors for changed passages together with their source versions. Keep a real question set that includes easy matches, difficult paraphrases and similar documents with different answers. Measure retrieval quality and the behavior of the complete search flow under the workload you expect. The Lite edition’s maker positioning helps choose a candidate; the final dimension, passage strategy and index settings come from the results on your material.
", "aboutText": "Voyage 3.5 Lite converts text into embeddings for semantic retrieval. Voyage AI describes this edition as optimized for latency and cost, making it a candidate for search experiences that embed incoming questions frequently or maintain a large collection of searchable passages. The output is a numerical representation of the supplied text, which a retrieval application compares with vectors stored for its source material.\n\nStart with a collection whose boundaries match the user’s task. For a help center, one passage might explain a procedure and its prerequisites. For a discussion archive, keep enough of a reply chain to identify what the response addresses. A result should lead to a readable piece of evidence, so store the original text, stable source link and document metadata with each embedding.\n\nWrite test queries as users would ask them. “Where do I change the address on an invoice?” is a more useful search check than copying the relevant article heading. Include short questions, paraphrases, domain abbreviations and cases that mention several concepts. Review the returned passages and identify whether a missed result comes from missing source content, poor passage boundaries or a retrieval choice.\n\nThe maker documents a 32,000-token context window. This capacity allows substantial text inputs, while passage length remains a design choice for the search experience. Keep a compact answer together with necessary conditions; avoid cutting a definition away from the term it explains. Extract readable text from the source and remove navigation repeated on every page when it obscures the information the user wants.\n\nVoyage 3.5 Lite supports 2,048, 1,024, 512 and 256 dimensions. Floating-point, eight-bit integer and binary representations provide additional choices for the vector index. Test a smaller or quantized representation against the same questions and corpus used for the full-precision baseline. Record the selected model, dimension and data type with the index so query vectors use the corresponding settings.\n\nIn the maker’s retrieval workflow, identify indexed passages as documents and incoming searches as queries. Preserve the mapping from every returned vector to its input text when processing several passages together. A successful embedding operation supplies vectors; the application still needs to put them in the correct records and expose the source excerpt when a user opens a result.\n\nUse this edition for a searchable support collection, a document-discovery tool or the retrieval stage of an assistant. For multilingual material, evaluate the language combinations present in your own collection rather than relying on a single English test. Keep permissions and locale metadata available to the application so a relevant match can be filtered and displayed in the right context.\n\nFor growing collections, update the vectors for changed passages together with their source versions. Keep a real question set that includes easy matches, difficult paraphrases and similar documents with different answers. Measure retrieval quality and the behavior of the complete search flow under the workload you expect. The Lite edition’s maker positioning helps choose a candidate; the final dimension, passage strategy and index settings come from the results on your material.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "691e62b204d966e66e4792cddf5b93a00e5df21c48adbbd1e6a2d8226b1c93ba", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "voyage-3.5-liteVoyage 3.5 Lite embeds text for semantic search with a focus on latency and efficient retrieval. It supports a 32,000-token context window, four vector sizes and quantized output for knowledge-base search, document matching and RAG.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Voyage 3.5 Lite converts text into embeddings for semantic retrieval. Voyage AI describes this edition as optimized for latency and cost, making it a candidate for search experiences that embed incoming questions frequently or maintain a large collection of searchable passages. The output is a numerical representation of the supplied text, which a retrieval application compares with vectors stored for its source material.
Start with a collection whose boundaries match the user’s task. For a help center, one passage might explain a procedure and its prerequisites. For a discussion archive, keep enough of a reply chain to identify what the response addresses. A result should lead to a readable piece of evidence, so store the original text, stable source link and document metadata with each embedding.
Write test queries as users would ask them. “Where do I change the address on an invoice?” is a more useful search check than copying the relevant article heading. Include short questions, paraphrases, domain abbreviations and cases that mention several concepts. Review the returned passages and identify whether a missed result comes from missing source content, poor passage boundaries or a retrieval choice.
The maker documents a 32,000-token context window. This capacity allows substantial text inputs, while passage length remains a design choice for the search experience. Keep a compact answer together with necessary conditions; avoid cutting a definition away from the term it explains. Extract readable text from the source and remove navigation repeated on every page when it obscures the information the user wants.
Voyage 3.5 Lite supports 2,048, 1,024, 512 and 256 dimensions. Floating-point, eight-bit integer and binary representations provide additional choices for the vector index. Test a smaller or quantized representation against the same questions and corpus used for the full-precision baseline. Record the selected model, dimension and data type with the index so query vectors use the corresponding settings.
In the maker’s retrieval workflow, identify indexed passages as documents and incoming searches as queries. Preserve the mapping from every returned vector to its input text when processing several passages together. A successful embedding operation supplies vectors; the application still needs to put them in the correct records and expose the source excerpt when a user opens a result.
Use this edition for a searchable support collection, a document-discovery tool or the retrieval stage of an assistant. For multilingual material, evaluate the language combinations present in your own collection rather than relying on a single English test. Keep permissions and locale metadata available to the application so a relevant match can be filtered and displayed in the right context.
For growing collections, update the vectors for changed passages together with their source versions. Keep a real question set that includes easy matches, difficult paraphrases and similar documents with different answers. Measure retrieval quality and the behavior of the complete search flow under the workload you expect. The Lite edition’s maker positioning helps choose a candidate; the final dimension, passage strategy and index settings come from the results on your material.
POST /v1/embeddingstextembedding| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits voyage-3.5-lite 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.0001 / 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.5-lite",\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.5-lite
Use the method paths shown above.