OpenAI compatible API. Attested gateway. Public status.

Zero Data Retention LLM API — Verifiable in Source

Zero data retention as a structural property of the open-source code, not just a contract clause. Multi-provider routing with the same posture.

Verify gateway

1 URLbase_url migration

100smodels and routes

0prompt logs by default

Zero data retention

Zero data retention as a verifiable property, not a contract clause.

"ZDR" usually means a clause in your enterprise agreement. The operator promises not to retain. You hope they comply.

TrustedRouter's prompt path never writes request or response bodies to persistent storage. The code that handles your prompts is open-source. The image hash is published. You can verify that retention is zero — without trusting us.

Try the playground Trust surface

What gets logged — schemaopen source

# Per-request record (token counts, timing, model id)
{
  "request_id": "req_...",
  "workspace_id": "...",
  "model_id": "anthropic/claude-sonnet-4.6",
  "input_tokens": 12,
  "output_tokens": 84,
  "cost_microdollars": 218,
  "provider": "anthropic",
  "region": "us-central1",
  "created_at": "..."
}
# What's NOT in here:
#   - prompt body
#   - response body
#   - user inputs of any kind
# Audit the schema:
#   github.com/.../storage_models.py

Structural

Zero, by construction.

The attested binary doesn't open a write handle to a prompt path. The retention isn't a policy choice; it's a structural property of the code.

Verifiable

Check it yourself.

Grep the source for any code that touches request bodies. There isn't any. The image hash you build is the hash the enclave reports.

End-to-end

Including upstream where possible.

For providers with their own ZDR posture (Anthropic, OpenAI Enterprise, Tinfoil, GCP Confidential), we route under their stronger guarantees and surface that on each model page.

Typical ZDR clauseTrustedRouter

EnforcementContractualStructural — in source

Audit pathSOC 2 + breach disclosureRead the open-source binary + hash check

Operator privilegeOperator can change behaviorOperator can't change without breaking attestation

Multi-providerPer-provider negotiationOne TR contract, route across providers

Self-hostUsually not availableYes — same attestation chain

The honest limits

What ZDR doesn't cover.

Upstream providers have their own retention behavior. We can route to providers that match your posture and we publish each one's known stance on the model pages.

Attestation proves the running binary is the published binary. It doesn't prove the binary is bug-free.

If you can't trust AWS or GCP's hardware root keys at all, the attestation chain doesn't save you. Cross-cloud helps — TR runs on both — but it doesn't eliminate the dependency.