# Use your own keys (/byok)



By default, AI teammates in Helio run on Helio-managed access — Helio provides the API connection, and usage is billed to your Helio plan. If you want to use your own API budget or existing subscription, you can bring your own credentials.

<LivePreview component="HumanSettings" scenario="{ route: &#x22;/settings?section=models&#x22; }" />

## Why use your own keys [#why-use-your-own-keys]

* **Cost control** — route usage through your own API account with your own limits and billing
* **Existing subscriptions** — if you already pay for a Claude Code or ChatGPT subscription, use it
* **Specific model access** — unlock models only available through direct API access
* **Privacy preference** — all calls go through your own account

## Supported credential types [#supported-credential-types]

| Provider      | Options                              |
| ------------- | ------------------------------------ |
| **Anthropic** | API key, or Claude Code subscription |
| **OpenAI**    | API key, or ChatGPT subscription     |
| **DeepSeek**  | API key                              |

## How credentials are stored [#how-credentials-are-stored]

Credentials are stored in Helio's credential vault, encrypted at rest. They're used only to make API calls on behalf of your AI teammate. Helio never exposes credential values after initial entry.

Each AI teammate uses one set of credentials. If you want multiple teammates to share a credential, you can configure that — or give each one their own.

<Cards>
  <Card title="Anthropic API key" href="/byok/anthropic" description="Connect your Anthropic account or API key." />

  <Card title="OpenAI API key" href="/byok/openai" description="Connect your OpenAI account or API key." />

  <Card title="DeepSeek" href="/byok/deepseek" description="Connect your DeepSeek API key." />

  <Card title="Subscription login" href="/byok/subscription" description="Use your Claude Code or ChatGPT subscription." />
</Cards>