Better trust
Match the hosted gateway to a public source commit and image digest before production traffic moves.
One OpenAI-compatible API for hundreds of open-weight and frontier models. Requests cross an attested gateway that does not log prompt or output content. Even our engineers cannot read your requests.
TrustedRouter is an OpenRouter alternative for teams that need verifiable privacy, lower-cost model choices, provider fallback, and one API across hundreds of models.
Match the hosted gateway to a public source commit and image digest before production traffic moves.
Use Qwen, GLM, DeepSeek, Google Gemma, Kimi, MiniMax, and other open models beside every frontier model.
Keep the OpenAI SDK and change one base URL. Agents can read llms.txt or use the MCP server.
Provider failover and regional routing keep one upstream outage from becoming your product outage.
Keep your existing OpenAI-shaped calls. Add privacy and routing constraints only when you need them.
trustedrouter/auto for healthy-provider rollovertrustedrouter/zdr for zero-retention routingtrustedrouter/e2e for confidential + E2EE provider routestrustedrouter/eu for Europe-focused routingfrom openai import OpenAI
client = OpenAI(
api_key=os.environ["TRUSTEDROUTER_API_KEY"],
base_url="https://api.allyrouter.com/v1",
)
response = client.chat.completions.create(
model="trustedrouter/auto",
messages=[{"role": "user", "content": "Hello"}],
extra_body={
"provider": {"min_privacy": "confidential"}
},
)
Named aliases make privacy, geography, cost, and failover explicit. Direct model IDs remain available when exact model selection matters.
| Model | Designed for | Routing policy |
|---|---|---|
trustedrouter/auto | General production traffic | Healthy provider rollover |
trustedrouter/zdr | Legal and sensitive work | Zero-retention providers |
trustedrouter/e2e | Confidential workloads | Confidential provider compute |
trustedrouter/eu | European workloads | EU-focused routes |
trustedrouter/synth | Combination models | Multiple models, one answer |
The production prompt path is separate from the dashboard and billing control plane. Every trust claim reduces to evidence you can inspect.
Regional gateways, provider health measurements, and explicit fallback keep failures visible and contained. The public status page separates router-core health from upstream model health.
Frontend, backend, gateway, infrastructure, SDKs, and deployment configuration are public. Hosted attestation connects that source to the code serving requests.
Use prepaid credits, BYOK, Stripe, PayPal, or stablecoin. Provider prices and routing costs remain visible before you call.