What “bring your own key” means
Bring your own key, usually shortened to BYOK, means connecting your own account or API credential from an AI provider, such as OpenAI, Anthropic, Google or others, to an agent, so that the agent uses your account to run its AI models rather than one bundled into a flat subscription. The billing goes straight to the provider you chose, at their rates, and the agent product itself typically charges separately for the parts of the service that aren’t the model itself: the workspace, the scheduling, the approvals, the memory and the receipts.
The term comes from “bring your own device” and similar patterns in software, where a product lets you supply your own resource instead of one it provides by default. For AI agents, that resource is model access.
How BYOK works in practice
To use BYOK, you generate an API key from a provider’s developer console, or connect an eligible account, and give that key to the agent product, usually stored securely and scoped to that specific use. From then on, tasks that use that provider’s model are billed to your account directly. Most agents that support BYOK also offer a bundled default, so you can mix: bring your own key for a provider you already use heavily, and rely on the product’s included access for everything else.
It’s worth being precise about one distinction here: a consumer subscription to a chat app (a monthly plan for using that provider’s own chat product) is usually not the same credential as an API key (a developer credential meant to authenticate a separate application). Some providers allow using a subscription this way; many don’t. Check what a given agent supports before assuming your existing subscription will work.
What BYOK gets you
BYOK gives you two things a bundled-only product can’t: direct visibility into what your AI usage costs, since it shows up on the provider’s own bill rather than folded into a flat subscription, and independence from any one product’s markup or model selection. If a product only offers models it has bundled, you’re paying whatever markup is built into that price and using whatever models the product has chosen to support, even if a different provider would suit a specific task better.
The tradeoff is a bit more setup, and the need to manage a provider account and a key yourself, which is why most agents that support BYOK also offer a bundled path for people who’d rather not.
BYOK vs. bundled model access
A bundled model is included in the product’s price: simpler to start with, generally more predictable month to month, but you’re limited to the models the product has chosen to offer, and you don’t see the underlying usage cost. A BYOK setup shows you the real cost of model usage, gives you access to whichever provider you’ve connected, and generally suits people already comfortable managing a provider account. Many agents, including model-agnostic ones, support both, letting you choose per provider rather than committing to one approach for everything.
What to look for in BYOK support
- Which providers are supported, since not every agent that mentions BYOK supports every provider.
- Whether a subscription or only an API key is accepted, since these are different credentials with different costs.
- How the key is stored and scoped, and whether you can revoke it without affecting anything else.
- Whether you can mix BYOK and bundled access across different tasks or providers.
- Whether usage is shown to you, so you can see what a task cost on your own account.
How OperatorNest approaches this
OperatorNest lets you bring your own subscription or API key for supported AI providers, or rely on a bundled default, and you can mix both across tasks. Model choice and billing stay visible per task, and switching between a bundled model and your own key doesn’t reset an operator’s memory or task history.