Access free and premium models through a single OpenAI-compatible endpoint.
Smart routing across Google, OpenAI, Anthropic, xAI / Grok, AWS Bedrock, Groq, and Cerebras - no model names to track. You pick what matters - the capability tier and the optimization direction. The router picks the model. When a cheaper option launches or a provider goes down, your requests adapt automatically. No model names to track. No code to change.
A 4% fee on credit deposits. Requests are billed at actual provider market rates - you pay what the model costs, nothing more. Every response includes X-Model-Router-Model and X-Model-Router-Provider headers so you always know exactly what ran and what it cost.
The auto routing tier selection is interesting, curious how it handles the credential surface area as you add providers. Each provider in the rotation is another API key that needs to exist somewhere in the request path.
With 7+ providers, the secrets management problem compounds: rotation schedules differ per provider, a compromised key at one provider doesn't invalidate the others, and CI/CD pipelines end up holding plaintext keys for all of them simultaneously.
Does the router hold the provider keys server side, or does the client pass them per request? The architecture doc doesn't make this clear.
Similar to OpenRouter, everything routes through this API gateway. You buy your token spend via this gateway. So, I believe you only need a single API key.
Access free and premium models through a single OpenAI-compatible endpoint.
Smart routing across Google, OpenAI, Anthropic, xAI / Grok, AWS Bedrock, Groq, and Cerebras - no model names to track. You pick what matters - the capability tier and the optimization direction. The router picks the model. When a cheaper option launches or a provider goes down, your requests adapt automatically. No model names to track. No code to change.
A 4% fee on credit deposits. Requests are billed at actual provider market rates - you pay what the model costs, nothing more. Every response includes X-Model-Router-Model and X-Model-Router-Provider headers so you always know exactly what ran and what it cost.
The auto routing tier selection is interesting, curious how it handles the credential surface area as you add providers. Each provider in the rotation is another API key that needs to exist somewhere in the request path. With 7+ providers, the secrets management problem compounds: rotation schedules differ per provider, a compromised key at one provider doesn't invalidate the others, and CI/CD pipelines end up holding plaintext keys for all of them simultaneously. Does the router hold the provider keys server side, or does the client pass them per request? The architecture doc doesn't make this clear.
Similar to OpenRouter, everything routes through this API gateway. You buy your token spend via this gateway. So, I believe you only need a single API key.