OpenAI compatible API. Attested gateway. Public status.

Providers

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

Verify gateway

1 URLbase_url migration

100smodels and routes

0prompt logs by default

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://api.trustedrouter.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.

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
Venice `venice`	Confidential	yes	yes	yes	yes	yes	Tracked as confidential — Venice documents no logging or storage of prompts/responses plus TEE-isolated, end-to-end-encrypted inference. (Caveat: requests Venice proxies to external frontier models inherit those providers' policies; TR routes Venice-native open models here.) 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
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 provider claim	yes	yes	no	not claimed	not claimed	Not currently marked ZDR in TrustedRouter. OpenAI may offer endpoint- or account-specific data-retention controls, but this provider is excluded from trustedrouter/zdr until that posture is reverified. Policy source
Gemini `gemini`	No provider claim	yes	yes	no	not claimed	not claimed	Not currently marked ZDR in TrustedRouter. Google Gemini / Vertex routes may have account- or product-specific data-governance terms, but this provider is excluded from trustedrouter/zdr until that posture is reverified. Policy source
Cerebras `cerebras`	No logs	yes	yes	yes	not claimed	not claimed	Tracked as provider-ZDR. Cerebras documents ZDR-compliant ephemeral prompt caching and no persisted prompt cache data. 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	Marked ZDR via TrustedRouter's arrangement — Together's ZDR is an opt-in account/privacy setting, NOT the public default, and the deployed Together account has it enabled. Together does not train on content without 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`	Confidential	yes	yes	yes	yes	yes	Tracked as a confidential AI provider with provider-side attestation and encrypted prompt transport. 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
Parasail `parasail`	No provider claim	yes	yes	not claimed	not claimed	not claimed	Parasail documents no input logging/storage for serverless and dedicated service paths, with different handling for batch service. 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
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
DeepInfra `deepinfra`	No logs	yes	yes	yes	not claimed	not claimed	Tracked as provider ZDR — DeepInfra documents memory-only handling with no storage of API content and no training on submitted API data. (Exception: requests to Google/Anthropic-backed models inherit those vendors' policies.) 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
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	no	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 zero-retention providers first, trustedrouter/eu for EU-focused provider selection, trustedrouter/e2e for confidential + E2EE routes, or provider routing filters for custom policy. Use trustedrouter/auto when breadth and health are the priority.