Vultr
Explore Vultr models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Vultrvultr
No provider claim
These privacy labels describe Vultr, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Vultr |
|---|---|
| Routing status | Not routable |
| Provider website | https://www.vultr.com/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | Not routable: the configured credential is rejected by both Vultr's account API and Serverless Inference API. Vultr issues a distinct inference key per subscription; the provider stays listed until that key is available. Policy source |
Models served by Vultr.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does Vultr have zero data retention?
TrustedRouter does not currently mark Vultr as provider-level zero data retention. Use trustedrouter/zdr or provider.min_privacy=zdr to select a different eligible route, and review the linked policy source for changes.
Is Vultr end-to-end encrypted?
TrustedRouter does not currently mark Vultr 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 Vultr models are available through TrustedRouter?
This page currently lists 0 public Vultr models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.