Service accounts
Use service accounts to give a script or tool its own key to your organization's models, separate from any person.
Feature Updated 19 Nov 2026Who can do this
Organizations on Enterprise Cloud. Owners and admins.
What a service account is
A service account is a login for a tool rather than a person, such as a build agent or a script. Use one when something other than a member needs your organization's models. It belongs to a team, and the team decides which models it may call.
A service account takes no seat and cannot sign in. It has its own keys and its own monthly budget. Its keys call your organization's models through an OpenAI-compatible API. That means any tool that takes an OpenAI key and a custom base URL can use it, such as n8n or Make. The keys reach your models and nothing else in PandaOS.
Where to find it
Open Service accounts in the console sidebar, under AI. The same list is also the Service accounts tab of Limits. Click an account's name to open its page, with its key and endpoint, keys, models, budget and usage.
Create a service account
You need: at least one team.
- Open Service accounts and click New service account.
- Enter a Name.
Name it after the tool, not a person. It must be unique in the organization and appears in usage reports. - Optional: enter a Description.
- Choose a Team.
Moving the account to another team later revokes its keys. - Click Create service account.
Add and reveal a key
Give each tool its own key, so revoking one never takes the others down.
- Open the account and click Add key.
- Enter a Name and click Create key.
Name it after what will hold it, for example "github-actions". The key starts as Creating. - When the key no longer shows Creating, click Reveal.
- In Ready to connect, copy the key, and the Base URL and Model id shown with it, before you close the dialog.
Warning: a key is shown once
Nobody can show it again in the console, including the admin who revealed it. If a key is lost, create a new key and revoke the old one.
Connect a tool
The Key and endpoint card at the top of the account's page has what a tool needs. That is the Base URL, the API key and the Model id, each with a copy button. A key you reveal stays filled in until you reload or leave the page. Use the model IDs exactly as listed, because a bare model name is refused. Example shows a request in curl, Python and Node.js, with your organization's values filled in.
In n8n: create an OpenAI credential with the key and the base URL from the card. In the chat model node, choose the model By ID and paste a model ID from the card.
Limits
- An account holds up to 10 keys.
- Its keys can call chat completions, the model list and embeddings, and nothing else. Image and voice models show in the account's Models box as "Not for service keys".
- There is no rotate. To replace a key, add a new one, give it to the tool, then revoke the old one.
- The account spends from one monthly budget shared by all its keys, set on the Service accounts tab of Limits. See Limits.
Narrow the models it may call
By default the account may call every model its team has. A model the team loses leaves the account too. An account narrowed only to models its team no longer has can call nothing until you choose again.
- Open the account and find the Models box.
- Tick the models it may call.
None ticked means every model its team has. - Click Save models.
Its keys pick up the change within a few minutes.
Budget and usage
The account's Budget and usage box shows its monthly budget and this month's spend, requests and tokens. It links to the Usage report for this account. The budget is shared by all its keys and is set on Limits: click Edit in Limits. If the budget shows Couldn't apply, click Retry in the same box.
Revoke a key
- Open the account from Service accounts.
- In the keys table, click Revoke on the key.
- Click Revoke key.
Anything using the key stops working within about a minute. A revoked key cannot be brought back.
Rename, move, suspend or delete an account
Use the account's row menu on Service accounts.
| Action | What happens |
|---|---|
| Rename | Its keys keep working. |
| Change team | All its keys are revoked and not replaced. Its model selection does not carry over, so after you add a new key it can call every model of the new team. |
| Suspend | All its keys are revoked. The account stays on record. |
| Reactivate | The account can hold keys again. The old keys do not come back, so add a new one. |
| Delete | Only possible once every key is revoked. Its recorded usage stays in the usage report under its name. |
Whatever uses a revoked key stops working until you create a new key and hand it over.
Use it from a PandaOS outside your organization
A PandaOS install that is not part of your organization can use the account as a custom endpoint. In that install, open Settings, then Models, and under Connections pick the Custom tab. Under Custom endpoints, click Add. Use the Base URL from the account's Key and endpoint card, and one of its keys. That install spends the account's budget, but no policy, team or seat applies to it.