Skip to main content

Replace a model account's API key

Replace the key when you rotate keys on a schedule, when an old key leaked or was revoked, or when the account's row shows ✕ or the no key chip. The account keeps its name, slug, settings and access: only the key changes, so tasks that pick it carry on as before. An account signed in with a subscription has no key; to renew one, see Sign a model account in again.

Who can do this: requires the Org Owner or Org Admin role. Anyone else sees the account under Read-only — only an administrator can change an account.

An API-key account's Details tab: API key reads Stored — leave blank to keep, above Workspace ID, Auto-assign, Cancel and Save

  1. Create the new key with your AI provider. Keep the old one working until step 7, so no run is left without a key.
  2. In the sidebar, select Directory, then AI Accounts.
  3. Select the account's name, or Edit in its ⋯ row menu. Its Details tab opens beside the list.
  4. Paste the new key into API key. The field never shows the stored key: it reads Stored — leave blank to keep, or No key stored when the key is gone.
  5. If the form shows Workspace ID, change it only when the new key belongs to another workspace. Leave it blank for a key scoped to its own workspace.
  6. Select Save. Jaah checks the new key with the provider before it stores it. A key the provider refuses, or one it can't reach, is not saved: the error shows above the form, and the old key stays.
  7. Check the account's row in the list: ● means the account is available again, and the no key chip is gone. Then revoke the old key with your provider.

Leaving API key blank keeps the stored key, so you can change the name or other settings without touching it. A new key takes over for runs that start after Save.