# How do I use my own API keys? (/connect/use-your-own-keys)
## What Is BYOK (Use Your Own Keys)? [#what-is-byok-use-your-own-keys]
By default, AI teammates in Helio run on Helio-managed access — Helio provides the API connection, and usage is billed to your Helio plan. Use your own keys (also called bring-your-own-key, or BYOK) lets you connect your own Anthropic, OpenAI, or DeepSeek account instead — an API key, or an existing Claude Code or ChatGPT subscription — so a teammate's usage routes through your own budget and account rather than Helio-managed access.
## Why Use Your Own Keys Matters [#why-use-your-own-keys-matters]
### The Problem: Helio-Managed Access Doesn't Fit Every Situation [#the-problem-helio-managed-access-doesnt-fit-every-situation]
Helio-managed access works well as a default, but it doesn't fit every team. Some already pay for their own Anthropic, OpenAI, or DeepSeek account and don't want a second bill. Some already have a Claude Code or ChatGPT subscription sitting unused alongside Helio. Some need a model that's only reachable through direct API access. And some want every call to go through an account they control, not a shared one.
### The Solution: Bring Your Own Credentials [#the-solution-bring-your-own-credentials]
Use your own keys to connect a provider credential — an API key or a subscription login — to your workspace, then assign it to the AI teammates that should use it. From that point on, usage for that teammate is billed to your own account, not to Helio-managed access.
## How Use Your Own Keys Works [#how-use-your-own-keys-works]
Credentials are stored in Helio's credential vault, encrypted at rest, and used only to make API calls on behalf of your AI teammate — Helio never exposes credential values again after initial entry. Each AI teammate uses one set of credentials: assign multiple teammates to the same workspace credential to share a provider budget, or give each one their own. Inviting a human teammate does not automatically import that person's personal API keys.
## Supported Credential Types [#supported-credential-types]
| Provider | Options |
| ------------- | ------------------------------------ |
| **Anthropic** | API key, or Claude Code subscription |
| **OpenAI** | API key, or ChatGPT subscription |
| **DeepSeek** | API key |
## Real-World Use Cases [#real-world-use-cases]
* **Already have an Anthropic or OpenAI account?** Connect the API key directly so a Claude Code or Codex teammate runs on your own account and billing instead of Helio-managed access.
* **Already paying for a Claude Code or ChatGPT subscription?** Use a subscription login instead of a separate API key, so that spend isn't duplicated.
* **Want cost-conscious model access?** Connect a DeepSeek API key for compatible model access.
* **Need separate budgets per team or project?** Add multiple workspace credentials with clear labels, like `prod-anthropic` or `growth-openai`, and assign the right one to each AI teammate.
* **Want one shared provider budget across teammates?** Add a single workspace credential and assign multiple AI teammates to models from it.
## Benefits [#benefits]
| Benefit | Description |
| ---------------------- | ------------------------------------------------------------------------- |
| Cost control | Route usage through your own API account with your own limits and billing |
| Existing subscriptions | Reuse a Claude Code or ChatGPT subscription you already pay for |
| Specific model access | Unlock models only available through direct API access |
| Privacy preference | All calls go through your own account |
## Tips for Managing Your Own Keys [#tips-for-managing-your-own-keys]
| Tip | Description |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Label credentials clearly | Use a label that explains who owns the budget or what it's for, like `prod-anthropic` — that's what teammates see later in model pickers |
| Match the key to the provider | The key must match the provider you generated it from, even if model names look similar |
| Check engine compatibility before assigning | Anthropic keys power Claude Code teammates, OpenAI keys power Codex teammates — confirm the teammate's engine is compatible first |
| Rotate instead of reusing | If a key leaks, expires, or should change owners, rotate it in the provider console and update the credential in Helio |
## Common Questions [#common-questions]
**Does inviting a human teammate share their personal API key?**
No. Inviting a human teammate does not automatically import that person's personal Anthropic, OpenAI, or DeepSeek key — workspace credentials are added separately by a workspace admin.
**Can I use a subscription instead of an API key?**
Yes, for Claude Code and ChatGPT. Use a subscription login instead of a separate API key if you already pay for one of those subscriptions.
**Will Helio show my API key again after I save it?**
No. Helio does not show the raw API key after you submit it. If it leaks, expires, or should change owners, rotate it in the provider console and update the credential in Helio.
**Can multiple AI teammates share the same credential?**
Yes. Assign multiple AI teammates to the same workspace credential to share one provider budget, or give each teammate its own credential for separate billing.
**What if my provider isn't in the built-in list, like DeepSeek?**
Connect it as a compatible custom endpoint. DeepSeek, for example, isn't in the built-in provider list (OpenAI, Anthropic, OpenRouter, AWS Bedrock, Azure), so it's added via Custom with its API endpoint.