Bring your own key
Merki can route inference through a provider key you already hold, instead of a hosted Merki model. This is called bring your own key, or BYOK.
Why use it
- Keep existing provider entitlements, commitments, or discounts.
- Meet a policy that requires inference to run on a vendor you have a direct agreement with.
- Compare a hosted Merki model against your own provider on the same requests.
Providers
BYOK works with keys from these providers:
| Provider | Supported |
|---|---|
| Anthropic (Claude) | Yes |
| OpenAI | Yes |
| Google (Gemini) | Yes |
| Mistral AI | Yes |
| Others | On request — tell us at enterprise@merki.dev |
How routing works
You register a provider key with Merki. Requests sent to a BYOK route are forwarded to that provider, and the response is returned to you. Merki applies the same key-safety and revocation rules to the route that it applies to Merki-issued keys. See API keys.
Model-name mapping is described in BYOK routing.
Billing
Tokens served by a BYOK provider are billed by that provider, under your agreement with them. Merki does not mark them up. The Merki routing fee is 0%. See Pricing.
Data handling
BYOK requests follow the same retention rules as hosted requests. See Zero data retention. The upstream provider processes the request under your own agreement with that provider.