OpenAI compatible API · Attested · Public status

Providers

Provider transparency for model compute, retention, confidential compute, and encrypted routes.

Verify gateway
Onebase URL to migrate
100sof models and routes
0prompt or output logs. Always.
Gateway boundaryTLS terminates inside TrustedRouter's attested gateway.
Provider computeEach upstream provider has its own retention and enclave posture.
No prompt logsTrustedRouter stores metadata and billing records, not prompts or outputs.
API metadataMachine readable JSON remains at https://gchircrcif.eu-west-3.awsapprunner.com/v1/providers.
Provider transparency

Trusted gateway first, then explicit provider claims.

Zero data retention, confidential compute, and encrypted provider routes are shown only when explicitly tracked. Unknown stays unknown.

List your models
Provider Trust tier Prepaid BYOK ZDR Confidential compute Provider E2EE Policy note
Tinfoil
tinfoil
Confidential yes yes yes yes yes Tracked as a confidential inference provider with attested provider compute and no prompt/output logging claims.
Policy source
TrustedRouter
trustedrouter
TR gateway yes no yes yes yes TrustedRouter's attested gateway stores no prompt or output content. Provider compute policy still depends on the selected upstream route.
Policy source
Meta via OpenRouter
meta
No provider claim yes no no no no TrustedRouter sends requests through its attested gateway to OpenRouter, which routes them to Meta. This downstream route is not marked zero-retention, confidential-compute, or end-to-end encrypted.
Policy source
Anthropic
anthropic
No provider claim yes yes no not claimed not claimed Not currently marked ZDR in TrustedRouter. Anthropic may offer contracted or account-specific data-retention terms, but this provider is excluded from trustedrouter/zdr until that posture is reverified.
Policy source
OpenAI
openai
No logs (prepaid) yes yes prepaid only not claimed not claimed Contracted Zero Data Retention is active for TrustedRouter's managed OpenAI account, effective July 28, 2026, and live enforcement was verified on July 29, 2026. This guarantee applies only to TrustedRouter-funded prepaid routes; customer BYOK credentials use the data controls on the customer's own OpenAI organization or project.
Policy source
Google AI Studio
google-ai-studio
No provider claim yes yes no not claimed not claimed Not currently marked ZDR in TrustedRouter. Google AI Studio and the Gemini Developer API have product- and billing-specific data-use terms, so this route stays outside trustedrouter/zdr.
Policy source
Google Vertex AI
google-vertex
No logs (prepaid) yes no prepaid only not claimed not claimed TrustedRouter's managed Vertex AI account is covered by contractual Zero Data Retention. This guarantee applies only to TrustedRouter-funded prepaid routes. TrustedRouter does not invoke Google Search or Maps grounding or Gemini Live session resumption on these routes. Google AI Studio is classified separately.
Policy source
Cerebras
cerebras
No logs yes yes yes not claimed not claimed Tracked as provider-ZDR. Cerebras documents zero-retention inference and ZDR-compliant ephemeral prompt caching that is never persisted.
Policy source
DeepSeek
deepseek
No provider claim yes yes no not claimed not claimed Not ZDR. DeepSeek's published privacy policy says prompts/inputs may be collected and personal data may be used to train or improve machine learning models and algorithms.
Policy source
Mistral
mistral
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. This is separate from any no-training or enterprise retention commitments Mistral may offer.
Policy source
Kimi
kimi
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Kimi/Moonshot policy source is linked for users who need to review API retention and processing terms.
Policy source
Z.AI
zai
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Z.AI/BigModel policy source is linked for users who need to review API retention and processing terms.
Policy source
Together
together
No logs yes yes yes not claimed not claimed Tracked as provider ZDR. Together documents that inference inputs and outputs are not stored by default; temporary prompt caching may be used for performance, and sharing content for training is opt-in.
Policy source
Fireworks AI
fireworks
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Fireworks publishes security, privacy, and zero-retention documentation; enable a contracted ZDR posture before marking this provider as ZDR.
Policy source
xAI Grok
grok
No provider claim yes yes not claimed not claimed not claimed xAI documents no training on API requests and 30-day default audit retention, with ZDR as an enterprise feature.
Policy source
Novita AI
novita
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Novita's privacy policy says personal information is not used for model training; customer-content processing is governed by customer agreements.
Policy source
Phala
phala
No logs yes yes yes yes no Phala publishes TDX/GPU attestation and signed request receipts, but TrustedRouter does not yet verify the complete receipt chain on every routed request. The route is therefore not classified as provider E2EE and is excluded from trustedrouter/e2e.
Policy source
SiliconFlow
siliconflow
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. SiliconFlow's privacy policy source is linked for retention and interaction-data terms.
Policy source
Venice
venice
No provider claim yes yes no no no Mixed model-specific posture. TrustedRouter cannot independently verify a complete chain from a live Venice endpoint through immutable source and hardware measurements to committed model weights. Venice is therefore not tracked as confidential or E2EE. Exact routes marked Private in Venice's live catalog qualify only as policy-backed ZDR through endpoint-specific records; Anonymized routes do not.
Policy source
Parasail
parasail
No logs yes yes yes not claimed not claimed Tracked as ZDR for serverless and dedicated inference. Parasail documents no storage or logging of submitted input on those service paths, retention only while generating and delivering output, and no training on input or output. Batch service is excluded from this claim; TrustedRouter does not route Parasail traffic through batch.
Policy source
Lightning AI
lightning
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Lightning's general privacy and security documentation is linked for retention review.
Policy source
GMI Cloud
gmi
No provider claim yes yes not claimed not claimed not claimed GMI runs isolated/VPC GPU inference, but that is network isolation, NOT an attested TEE — so no confidential-compute, zero-retention, or E2EE claim is marked. Retention/training terms are unverified (the published policy page is JavaScript-only and would not render).
Policy source
FriendliAI
friendli
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Friendli's legal/privacy terms are linked for users who need to review API data handling.
Policy source
Baseten
baseten
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Baseten's inference and security documentation are linked for users who need to review API data handling.
Policy source
Telnyx
telnyx
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR or confidential-compute claim is tracked here. Telnyx's privacy policy is linked for users who need to review inference data handling.
Policy source
Wafer
wafer
No provider claim yes yes not claimed not claimed not claimed Wafer supports request-scoped ZDR via Wafer-ZDR: required on supported models; model-level support differs, so TrustedRouter keeps provider-level claims conservative.
Policy source
Crusoe
crusoe
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Crusoe's Managed Inference docs and pricing/catalog pages are linked for model and API data-handling review.
Policy source
Makora
makora
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Makora's inference and privacy documentation are linked for users who need to review API data handling.
Policy source
Chutes
chutes
No logs yes yes yes yes no Chutes documents no prompt/output storage or training and serves these routes in confidential-compute TEEs. Standard API calls are not marked provider end-to-end encrypted.
Policy source
DigitalOcean Gradient AI
digitalocean
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. DigitalOcean's Gradient AI model and pricing documentation is linked for data-handling review.
Policy source
Cloudflare Workers AI
cloudflare-workers-ai
No provider claim yes no not claimed not claimed not claimed No provider-ZDR claim is tracked here. Cloudflare's Workers AI documentation is linked for model and data-handling review.
Policy source
Inceptron
inceptron
No logs yes no yes not claimed not claimed Inceptron documents zero retention by default: API prompts and outputs are processed transiently and discarded after processing.
Policy source
Morph
morph
No provider claim yes no not claimed not claimed not claimed Morph's public paid tier documents up to 30 days of content retention. Zero retention is reserved for enterprise contracts.
Policy source
Atlas Cloud
atlas-cloud
No provider claim yes no not claimed not claimed not claimed Atlas Cloud publishes a platform zero-retention policy, while its aggregated model routes can involve downstream providers. TrustedRouter keeps the public route tier conservative pending downstream-path contractual verification.
Policy source
StreamLake
streamlake
No provider claim yes no not claimed not claimed not claimed No provider-ZDR claim is tracked. StreamLake's public privacy policy is linked for API data-handling review.
Policy source
Neurometric AI
neurometric
No provider claim yes no no no no Neurometric states that TrustedRouter requests run with upstream trace logging disabled: prompts and completions are not written to observability or object storage, and only aggregate request counts and token totals are retained. This is classified as no-store, not contractual ZDR or confidential compute.
Policy source
DeepInfra
deepinfra
No provider claim yes yes no not claimed not claimed Tracked as no-store, not strict ZDR. DeepInfra documents memory-only handling and no training for ordinary inference, but reserves the right to log a small portion of requests for debugging or security. Google- and Anthropic-backed routes also inherit those vendors' terms.
Policy source
Nebius Token Factory
nebius
No logs yes yes yes not claimed not claimed Marked ZDR via TrustedRouter's arrangement — Nebius RETAINS inputs/outputs by default (for speculative decoding); zero retention is an opt-in control, which the deployed Nebius account has enabled. Nebius does not train on customer data.
Policy source
MiniMax
minimax
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. MiniMax's product privacy overview is linked for users who need to review API/open-platform terms.
Policy source
Thinking Machines Lab
thinkingmachines
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Thinking Machines Lab's model and pricing documentation is linked for model capability and API review.
Policy source
Xiaomi MiMo
xiaomi
No provider claim yes yes not claimed not claimed not claimed No provider-ZDR claim is tracked here. Xiaomi MiMo's open-platform terms are linked for users who need to review API data handling.
Policy source
Alibaba Cloud Model Studio
alibaba
No provider claim yes no not claimed not claimed not claimed No provider-ZDR claim is tracked here. Alibaba Cloud Model Studio model availability and pricing are linked for users who need to review API data handling and regional deployment scope.
Policy source
Cohere
cohere
No logs yes yes yes not claimed not claimed Marked ZDR — Cohere does not retain prompt/response content for TrustedRouter's configured account and does not train on customer API data. (Not a confidential-compute/TEE provider.)
Policy source
Voyage AI
voyage
No logs yes yes yes not claimed not claimed 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
What TR proves

The router path is verifiable.

The hosted API publishes source commit, image reference, and digest for the attested gateway. The control plane does not terminate prompt traffic.

What providers prove

Provider policy is separate.

If compute runs on Anthropic, OpenAI, Gemini, Phala, Tinfoil, or another upstream, that provider's policy controls model handling.

Routing

Choose privacy posture explicitly.

Use trustedrouter/zdr for the zero-retention pool, trustedrouter/eu for EU-focused provider selection, or trustedrouter/e2e for the confidential + E2EE pool. When selecting a model or provider directly, set provider.min_privacy = "zdr" or the stronger provider.min_privacy = "confidential"; these hard filters fail closed if no eligible endpoint remains. Use trustedrouter/auto when breadth and health are the priority.

Workspace access

Sign in

Choose a sign in method. New email and OAuth accounts include $0.10 in starter credit; wallet-only accounts start at $0.

By signing in you agree to the terms of service and privacy policy.