Skip to main content
A router needs one provider key source for each provider represented by its enabled models. For each provider, you can use a Managed key or bring your own OpenAI, Anthropic, or OpenRouter key. BYOK provider keys are stored encrypted and are never shown again after you save them.

​
Required Providers

If the router enables these models: 
[
  "openai/gpt-5.5",
  "anthropic/claude-sonnet-4-6",
  "openrouter/google/gemini-3.1-pro-preview"
]
then it needs a key source for OpenAI, Anthropic, and OpenRouter. You can mix sources; for example, use Managed OpenAI and Anthropic keys while bringing your own OpenRouter key. In the dashboard, that means:
ProviderKey source
OpenAIManaged
AnthropicManaged
OpenRouterBYOK

​
Choose Key Sources In The Dashboard

Open the router detail page and go to Keys. For each enabled provider, choose Managed or BYOK. If you choose BYOK, enter that provider’s API key. Blank BYOK fields keep existing user-supplied keys when editing a router, so enter a new key only when adding or replacing that provider’s stored key.

​
Runtime Behavior

Your application sends only the Dari routing API key to the router endpoint. It does not send provider keys per request. After the router selects a model, Dari uses the configured key source for that model’s provider. Managed keys are supplied by Dari; BYOK keys use the encrypted provider credential stored on the router.