Overview
LLM Keys are API keys that authenticate requests to the Aptible LLM Gateway. Each key is scoped to your organization, so a single key gives you access to every model allowed by your organization’s Model Access Policy. You don’t need separate keys per environment, application, or provider.Creating a Key
Go to LLM Gateway and select Create Key. Enter a name (handle) for the key. To cap what the key can spend, also enter a spend limit. Leave it blank to let the key spend up to your organization’s global spend limit. When you create a key, you become one of the new key’s owners by default. To share the key with teammates, either add them in the Owner field when you create the key, or add them later from the key’s Settings tab.
Claude Code
OpenAI-compatible SDKs
Anthropic-compatible SDKs
Managing Keys
Keys are managed from LLM Gateway in the Aptible dashboard. From the key list you can see each key’s name, status, current usage, and owner. If a key has several owners, hover over the owner column to see all of them. Select any key to view its details, including its owners, token usage, and costs.Key Owners
Each key must have one or more owners assigned to it. Being a key owner means:- You can manage the key — Key owners, Account Owners, and Deploy Owners are all able to manage the key. They can edit its settings, change its owners, and revoke it. They can also view the full records of its requests, including prompts and responses. See Permissions below.
- You get spend alerts — Spend alerts for a key go to its owners.
Changing a Key’s Owners
- Select the key from LLM Gateway and open its Settings tab.
- In Key Owners, change the owners:
- To add an owner, choose a member from the Select existing user… list, then select Add owner.
- To remove an owner, select Remove next to them.
- Each change is saved as soon as you make it.
- Every owner must be a member of your organization.
- A key needs at least one owner, so you can’t remove its last owner.
- If you remove yourself, you can no longer manage the key or view its full request records unless you are also an Account Owner or Deploy Owner keep that access.
When an Owner Leaves Your Organization
Aptible checks key owners against your organization’s members every hour. Anyone who has left your organization, including through SCIM or SSO, is removed as an owner of their keys. If an active key is left with no owners through this process, Aptible will notify your organization’s Account Owners. But the key will continue to function. Until it has an owner again, only Account Owners and Deploy Owners can manage it, and its spend alerts go to the Account Owners. To resolve it, add new owners as described in Changing a Key’s Owners, or revoke the key if it’s no longer needed.Editing a Key
To rename a key or change its spend limit, you must be one of its owners, an Account Owner, or a Deploy Owner. Select the key from LLM Gateway and open its Settings tab. Edit the Handle or the spend limit, then select Save Changes. To remove the key’s spend limit, clear the field. Each key’s handle must be unique within your organization. Renaming a key doesn’t change its token, so applications that use the key keep working. A revoked key can’t be edited.Revoking a Key
To revoke a key, select Revoke next to it in the LLM Gateway key list. You can also open the key’s Settings tab, enter the key’s handle to confirm, and select Revoke Key. Revoking a key immediately invalidates it. Use this if a key is compromised or you need to permanently cut off access for a specific application or team. A key’s owners, Account Owners, and Deploy Owners can revoke it. See Permissions below.Permissions
Any member of your organization can create an LLM Key and view every key’s metadata. Key creation and visibility aren’t restricted to account owners.The first time anyone in your organization creates a key, they will be required to accept a one-time notice about processing PHI through the gateway.
- Editing the key’s handle or spend limit
- Changing the key’s owners
- Revoking the key
- Viewing the full records of the key’s requests

