Voyage AI
Try Voyage AI on us. Starter credit covers your first requests, then one key reaches the Voyage AI model, with its privacy posture shown on the route.
Voyage AIvoyage
These privacy labels describe Voyage AI, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.
| Provider | Voyage AI |
|---|---|
| API operator country | US Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Active |
| Provider website | https://www.voyageai.com/ |
| Models | 1 public model |
| Credits routes | 1 |
| Zero data retention | yes All routes |
| Verified confidential inference | Not verified |
| Policy note | Marked ZDR — Voyage AI does not retain prompt content for TrustedRouter's configured account and does not train on customer API data. (Not a confidential-compute/TEE provider.) Policy source |
Inference locations
Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.
usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.
Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.
- Declared countries or regions
- Not verified
No inference-location declaration has been verified for this provider. - Can locations change?
- Not verified. Do not assume that the serving location is fixed.
- Provider region pinning
- Not verified.
- Pinning through TrustedRouter
- No verified provider-specific location pin documented here.
- Infrastructure declaration
- Inference location not verified; no country-specific residency commitment.
- Evidence
- Not yet reviewed.
Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.
Models served by Voyage AI.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
voyage/voyage-3-largeVoyage 3 Large |
— | 32,000 | $0.1899/1M | Not published | selected route |
Questions
Does Voyage AI have zero data retention?
TrustedRouter records Voyage AI as supporting provider-level zero data retention based on the policy source linked on this page. This is a provider policy claim, separate from TrustedRouter's content-stateless real-time gateway and from end-to-end confidential compute.
Is Voyage AI end-to-end encrypted?
TrustedRouter does not currently mark Voyage AI as end-to-end encrypted at the provider boundary. The TrustedRouter gateway is still attested, but the selected provider normally receives the request in order to run the model. Use trustedrouter/e2e for the stronger route requirement.
Which Voyage AI models are available through TrustedRouter?
This page currently lists 1 public Voyage AI model, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.