Telluvian
Explore Telluvian models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Telluviantelluvian
These privacy labels describe Telluvian, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Telluvian |
|---|---|
| API operator country | Not verified Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Active |
| Provider website | https://telluvian.ai/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | no |
| Verified confidential inference | Not verified |
| Policy note | Polyphemus sends the conversation and tool definitions to Telluvian for model selection. No ZDR or confidential-compute claim is made. 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.
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.
Measured performance
63 samplesContinuously sampled across Telluvian's routed models: p50 TTFT, effective throughput, and success rate. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime. No prompt or output content stored.
| p50 TTFT | — |
|---|---|
| Effective throughput | — |
| Uptime | 90.48% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| trustedrouter/polyphemus-1.0 | — | — | 90.48% | — | 63 |
Telluvian performance history · Full provider & model leaderboard.
Models served by Telluvian.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does Telluvian have zero data retention?
TrustedRouter does not currently mark Telluvian 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 Telluvian end-to-end encrypted?
TrustedRouter does not currently mark Telluvian 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 Telluvian models are available through TrustedRouter?
This page currently lists 0 public Telluvian models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.