Skip to content
WhoseDev logoWhoseDev Docs

Bring your own provider

Bring your own provider (BYOK) sends AI requests directly to a provider account you control. WhoseDev stores your API key securely on this device; billing and data retention follow the provider’s terms for your account.

Configure BYOK in WhoseDev AI Settings → Providers, or during first-run setup.

Supported providers

Section titled “Supported providers”
Provider Required fields Default endpoint
OpenAI API key https://api.openai.com/v1
Anthropic API key https://api.anthropic.com
OpenRouter API key https://openrouter.ai/api/v1
Google Gemini API key https://generativelanguage.googleapis.com
Azure OpenAI API key, endpoint, deployment name Your Azure resource URL

Azure OpenAI

Section titled “Azure OpenAI”

Azure connections require three values beyond the API key:

  • Endpoint — HTTPS base URL for your Azure OpenAI resource
  • Deployment name — the deployed model name in Azure
  • API version — defaults to 2024-10-21 if not specified

What BYOK covers

Section titled “What BYOK covers”

Direct-provider routes apply to chat, agent, and inline features where you select a BYOK model in the picker. Requests go to the provider you configured — not through WhoseDev-managed inference.

WhoseDev shows a source badge in the model picker so you can distinguish managed cloud models from BYOK and local models.

BYOK models appear when a connected key lists a model that matches WhoseDev’s catalog. The same catalog model can qualify on more than one connection (for example OpenAI and OpenRouter). Dated snapshots and fine-tuned ids (ft:…) match only when the catalog lists that exact id. Provider keys never leave this device.

AWS Bedrock

Section titled “AWS Bedrock”

AWS Bedrock BYOK for Ask/Plan/Act agent sessions is not available in current builds. If you configure Bedrock for agent runtime, WhoseDev returns an explicit unsupported error rather than silently using WhoseDev credits.

For agent work today, use Anthropic, OpenAI, Google, OpenRouter, or another supported BYOK provider, or switch to WhoseDev-managed models.

Security and billing

Section titled “Security and billing”
  • API keys are stored on this device using the editor’s secret storage.
  • WhoseDev does not charge WhoseDev credits for successful BYOK requests — your provider bills you directly.
  • Review your provider’s data retention and logging policies before using BYOK in repositories with sensitive code.

Advanced model catalog

Section titled “Advanced model catalog”

Run WhoseDev: Open Advanced Model Catalog to browse the full managed catalog separately from BYOK configuration. BYOK model lists are fetched from your provider when you connect.

Section titled “Related topics”