BYOK Deep Dive: Using Your Own API Keys with OpenModex
Learn how to bring your own API keys from OpenAI, Anthropic, and Google while still leveraging OpenModex routing, analytics, and reliability features. Ideal for teams with existing provider agreements.
Yuki Tanaka
Head of Product
Many teams already have direct relationships with AI providers -- negotiated pricing, committed spend agreements, or specific compliance requirements. Bring Your Own Key (BYOK) lets you use these existing arrangements while still benefiting from OpenModex routing, analytics, and reliability.
Setting Up BYOK
Setting up BYOK is simple. In your dashboard, navigate to Settings, then Provider Keys, and add your API keys for OpenAI, Anthropic, Google, or any supported provider. OpenModex encrypts your keys using AES-256 and stores them in a dedicated secrets vault.
How Billing Works
When BYOK is enabled for a provider, OpenModex routes requests to that provider using your key instead of ours. You get billed directly by the provider at your negotiated rates, while OpenModex only charges its platform fee (which is waived for Enterprise plans).
Unified Analytics
The analytics dashboard tracks usage and costs across both BYOK and OpenModex-managed keys, giving you a unified view of your AI spend. You can even compare the effective cost of using your own keys versus OpenModex managed pricing to optimize your strategy.
Seamless Integration
BYOK works seamlessly with all OpenModex features including Smart Routing, semantic caching, and failover. If your BYOK key hits a rate limit, OpenModex can automatically fall back to its managed pool, ensuring uninterrupted service.
Availability
BYOK is available on Pro and Enterprise plans. Enterprise customers can also configure team-level key policies, restricting which team members can use BYOK keys and which providers they can access.