Your personal AI key, budgets and revoking a key
A personal key is the credential a person's AI tools use to reach StackJack's AI gateway (see Setting up the AI gateway). It is StackJack's own credential, not a vendor key: it works only at the…
Written By Christopher Scaminaci
Last updated 4 days ago
A personal key is the credential a person's AI tools use to reach StackJack's AI gateway (see Setting up the AI gateway). It is StackJack's own credential, not a vendor key: it works only at the gateway, it is never passed on to the AI vendor, and StackJack can switch it off at any moment without touching your vendor accounts.
At a glance
- What it does: gives each person their own key to the AI gateway and the MCP proxy, with a budget you can set.
- Plan: Business and above, because it belongs to the gateway.
- Who: an Administrator gives seats and sets budgets. Staff collect their key.
- Where: AI Governance → AI traffic → AI gateway. Staff see their key on My AI activity. Budgets show on Activity → Spend.
A key looks like sjk_us_ followed by a long random text (sjk_eu_ in the Europe region). The part after the region word is the secret.
Getting a key
A person gets a key in two steps.
- An administrator gives the person a seat in the Personal keys section of AI Governance → AI traffic → AI gateway: Give a seat for one person, or Give every staff member a seat. A seat is a promise of a key. It holds no secret yet.
- The person reveals the key themself. They open My AI activity, then My activity and find the card Your AI gateway key. The card appears only when your organization has the AI gateway switched on. They select Show my key. A person who reaches their page through the single-person link in their email can do the same.
The key is shown once. The card says "This is the only time the key is shown. Copy it now." and offers a copy button, the address of the gateway, and one-line commands that put the key where Claude Code and Codex read it. Selecting I have saved the key closes the panel. Cursor and VS Code get the manual steps instead (see Setting up the AI gateway).
StackJack does not keep the key text anywhere. It keeps the first eight characters after the region word, so you can tell keys apart (for example sjk_us_AbCdEfGh), and a one-way fingerprint that lets the gateway recognise the key. Nobody at StackJack can show a lost key again. If a person loses theirs, an administrator selects Reissue next to it: the old key stops and the person gets a new seat to reveal.
A seat is revealed once. If two windows ask for the key at the same moment, only one of them makes the key.
Agents. A bot or automation is not a person. Under Personal keys, type the agent's name and select Make the key. The key is shown once, to the administrator, who puts it in the agent's settings. An agent key is never counted as a member of your staff. Reissue replaces it with a new key of the same name.
Keys made in the Portal are not limited to particular models or vendor keys, and they do not expire by themselves. Revoke or reissue a key when its owner no longer needs it. When you erase a person (see Erasing a person), their keys are revoked.
What a key is used for
Each call made with a key is recorded under the person who owns it (or under the agent), with the tool the call came from, the vendor, the model, the token counts and the cost. The person's name is shown according to your naming settings; see Capture levels and privacy. What is recorded about the text of the call depends on the capture level of the AI gateway source.
Budgets
A budget is a monthly limit on what the gateway lets your people spend. Set budgets in the Budgets panel of AI Governance → AI traffic → AI gateway. A budget has a name, a monthly limit in US dollars and a scope:
How it is counted:
- The period is the calendar month in UTC. A new month starts every budget at zero.
- Spend is the vendor's own token counts times a price table. A call to a model that is not in the table is allowed and shown as unpriced. It is not counted, and it never trips a hard stop.
- A person's spend is counted only when your staff notice allows collecting it (see Capture levels and privacy). The organization, tool and vendor totals are your own money and are always counted.
- You can have up to 100 budgets. Changing a budget's scope, people or limit starts its alerts again for the month.
The alerts at 50, 80 and 100 percent
When a budget's spend reaches 50, 80 and 100 percent of its limit, StackJack raises one alert for each threshold, once per month. They appear in the alert inbox for your administrators and go out through the alert channels you set up. A jump from 40 to 85 percent raises the 50 and the 80 together. The alert says which budget; it names no text.
The people who use the gateway do not see these alerts.
The hard stop
A budget can have a hard stop. Without one, it only alerts. With one, the gateway refuses calls once the limit is reached, until the month ends or you raise or remove the limit. The tool shows: "The AI budget for this account is used up, so StackJack stopped this request."
A hard stop applies to the AI gateway only. It is enforced from a copy of your settings that the gateway refreshes about once a minute, and every gateway server counts its own calls, so spend can go a little past the limit before the stop takes hold. StackJack records when it sees spend above a hard limit.
Revoking a key
On Personal keys, select Revoke next to the key. Or ask an assistant that has the StackJack tools to revoke it (administrators only).
- It stops within a minute or two. The gateway learns of the revoke when StackJack next refreshes its copy of your settings. After that, a call with the key is refused with "This personal key was revoked."
- The key keeps reading as revoked for seven days. After that the gateway no longer lists it and answers "StackJack does not recognise this personal key."
- Revoking is safe to repeat. Revoking a key that is already revoked changes nothing and writes no second entry.
- The audit trail records who revoked the key and when. It never records the key.
- A key that was made with an end date stops on that date with "This personal key has expired."
To give the person a working key again, use Reissue.
Related: Setting up the AI gateway, Setting up the MCP proxy (the same key opens approved MCP servers), What staff can see about themselves.
Was this helpful?
More in Connect your AI
Data sourcesSend telemetry from coding toolsSettings for staff machinesDelivering the settings through your RMMStill need help? Ask the team