Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Voyage AI / Multimodal embeddings

Voyage multimodal 3

Earlier shared embeddings for interleaved text and images.

Embeddings
availableClosed weightsEmbeddings
Official documentation (opens in a new tab)Reviewed 13 Oct 2026
6 of 18 specification fields collected
Input token limit32K32,000 tokens
Vector dimensions1024See specification notes below
Input billingSee ratesVoyage API
Output billingSee ratesPublished units and conditions below

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
32,000 tokensSource for Context / input limit (opens in a new tab)

Per input or chunk. Aggregate request limits are separate.

Maximum output
Not collected
Input modalities
Text, ImageSource for Input modalities (opens in a new tab)
Output modalities
EmbeddingsSource for Output modalities (opens in a new tab)
Reasoning
Not collected
Tool calling
Not collected
Structured output
Not collected
Streaming
Not collected
Batch processing
Not collected
Fine-tuning
Not collected
Knowledge cutoff
Not collected
Release date
2024-11-12Source for Release date (opens in a new tab)

Official release announcement date.

Parameters
Not collected
Architecture
Not collected
Languages
Not collected
Context caching
Not collected

No model-specific cache eligibility, retained-prefix lifetime or discounted cache rate established in the reviewed documentation.

Embedding dimensions
1024Source for Embedding dimensions (opens in a new tab)
Image input limits
Up to 16 million pixels and 20 MB per imageSource for Image input limits (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.

Voyage API

Provider source (opens in a new tab)
API model ID
voyage-multimodal-3
Access
Voyage API key; account-specific usage and rate limits apply.
Regions
Contractual residency and serving-region guarantees require verification.
API endpoint URL
https://api.voyageai.com/v1/multimodalembeddingsSource for API endpoint URL (opens in a new tab)
Total request input
320,000 tokens across up to 1,000 inputsSource for Total request input (opens in a new tab)
Visual context accounting
Context usage: one token per 560 image pixels.Source for Visual context accounting (opens in a new tab)

Context accounting is separate from pixel-based billing.

Prices retain their published currencies and billing units below.

Published billing units · original currency · observed 13 Oct 2026
CategoryUsageRateUnit
embeddingsText embedding1$0.121M text tokens
embeddingsImage embedding2$0.601B pixels

Rate conditions

  1. The first 200M text tokens are free per account under the published allowance; subsequent input tokens are charged at this rate.
  2. Each image is billed at a minimum of 50,000 and maximum of 2 million pixels. Video frames are individually treated as images where supported. Published allowance: 150B pixels per account. Do not convert this into a flat video-second rate.
Pricing source (opens in a new tab)

Data & enterprise terms

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.

Read the service policy (opens in a new tab)

Caching

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-multimodal-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.

Classification evidence (opens in a new tab)

Lifecycle dates

Release announced12 Nov 2024Source (opens in a new tab)

Sources reviewed