OpenAI compatible API. Attested gateway. Public status.

Claude API Privacy — Through TrustedRouter

Call Anthropic Claude through a hardware-attested, open-source router. Anthropic's privacy posture plus a routing path you can verify.

Verify gateway
1 URLbase_url migration
100smodels and routes
0prompt logs by default
Claude API privacy

Call Claude through a prompt path you can verify.

Anthropic's privacy posture is one of the best in the industry. But the path between your code and Anthropic still matters — and most routing layers are closed-source black boxes.

TrustedRouter routes to Claude (and 30+ other providers) through a hardware-attested, open-source gateway. Anthropic's privacy claims plus a verifiable router on top.

Try Claude Sonnet in the playground How attestation works

Claude via TRAnthropic + OpenAI SDKs
# Anthropic SDK
from anthropic import Anthropic
client = Anthropic(
    base_url="https://api.trustedrouter.com",
    api_key="sk-tr-v1-..."
)

# Or via OpenAI-compat SDK
from openai import OpenAI
client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

resp = client.chat.completions.create(
    model="anthropic/claude-sonnet-4.6",
    messages=[{"role": "user", "content": "hi"}],
)
No router logs

TR doesn't store your prompts.

Attested gateway never writes request or response bodies. Verifiable in source. Anthropic's own privacy policy applies upstream.

Models you want

Sonnet 4.6, Opus 4.7, Haiku 4.5.

Plus the older 3.x family, plus the full models from OpenAI, Google, Meta, Mistral, Z.AI, DeepSeek, Kimi, MiniMax. Same API, one key.

Verifiable

Hash-check the gateway image.

Fetch /attestation, grab the image_digest, compare to the published artifact. Now you know what code is between you and Anthropic.

When you'd use TR for Claude

You want Anthropic + something more.

Audit-driven routing. Your security team needs to read the router code. Anthropic's API is closed; TR's router is open.

Provider fallback. Anthropic has occasional API hiccups. TR's pool falls over to GPT, Gemini, or other Claude-class models on a hard failure.

Comparison playground. Try the same prompt across Claude, GPT, Gemini, Kimi side-by-side at trustedrouter.com/chat — no per-provider setup.

Unified billing. One TR contract, one invoice, one usage dashboard. No per-provider account sprawl.

Self-host. Run TR inside your own VPC for HIPAA, FedRAMP, or air-gapped environments. Anthropic-via-TR still works because the routing image is verifiable.

Anthropic directClaude via TR
Anthropic privacy postureAnthropic's policyAnthropic's policy (passthrough)
Router coden/aOpen source, attested
Multi-modelClaude onlyClaude + 30 more providers, same API
FailoverManualAutomatic on hard failures
Unified billingPer-providerOne invoice

Sign in

Choose a sign in method.