Bring your own key or subscription

You can run model requests on your own provider account instead of Alfe’s pooled access. The provider bills you directly, and Alfe doesn’t deduct credits for those requests. If you don’t add anything, pooled access works out of the box.

When to bring your own credentials

Your own credentials make sense when you:

Have negotiated rates, committed spend, or provider credits to use up.
Need requests to run under your own account for compliance or contractual reasons.
Already pay for a Claude or Codex subscription that an agent can use.

Add an organization-wide provider key

A provider key applies to requests for that provider across your account. Other providers stay on pooled access.

Open AI Models in the dashboard.
Under Provider API Keys (BYOK), select the provider and enter your key.
Select Save key.

You need permission to manage the model policy to see this section. If you remove a key, future requests for that provider fall back to the next available credential.

Add a credential to one agent

Agents on a terminal runtime can hold their own credential, which applies to that agent only. You’ll find these options in the agent’s Settings tab:

Claude Code — your own Claude subscription token or Anthropic API key.
Codex — your own Codex subscription, used for eligible GPT model requests. Without one, OpenAI requests use your organization’s API key or Alfe credits.
Other terminal runtimes — the API key for that runtime’s provider.

Without an agent credential, a managed agent uses Alfe credits. A self-hosted agent tries the runtime’s login on its own machine first, then Alfe credits.

See where usage ran

The Usage page splits an agent’s activity by source, so you can check that a credential is being used. Costs shown for your own key or subscription are estimates, because the provider bills them.