Automatic chunking defaults off. Default chunk size 512 tokens and overlap 0; overlap must be smaller than chunk size. Overlapping tokens are billed.Source for Document chunking (opens in a new tab)
Access & pricing
Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.
Up to 1,000 inputs and 16,000 chunks per request. Automatic chunking requires input_type=document and flat strings; do not combine it with client-side chunk_fn.Source for Request limits (opens in a new tab)
Prices retain their published currencies and billing units below.
Published billing units · original currency · observed 13 Oct 2026
Category
Usage
Rate
Unit
embeddings
Text embedding1
$0.18
1M tokens
Rate conditions
Input text tokens only, not generated output. Current pricing tables take precedence over inconsistent introductory free-credit examples. Older-model table entries have no free token allowance.
The FAQ describes an opt-out from storage and future training that enables zero-day retention on Voyage-hosted model API endpoints. This is an opt-out option, not a verified account default.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Files are retained for 30 days before automatic deletion. Storage costs $0.05 per GB per month. Do not apply online endpoint retention choices to batch files automatically.
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
Voyage API
voyage-context-3
Not verified
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Voyage Batch API
voyage-context-3
Not verified
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
Inferred for this exact native release from provider API documentation and the provider-owned public repository inventory. Published tokenizer/configuration files are not model weights. The explicitly open-weight Voyage 4 Nano is excluded; no weight artifact for this identity was identified.
