Working with tokens

One token per tool

A token identifies you, not a device. Issuing one per tool means you can revoke a single integration — a laptop that was lost, a CI runner that was retired — without breaking everything else you use.

Rotating safely

Create the replacement first, update the tool, confirm traffic is flowing on the new token in the request log, and only then revoke the old one. Revocation takes effect at once on every gateway replica.

Token context

Each token works either as Personal or as one of your teams, chosen when you create it. The context decides which models and quotas the token uses, whatever team you have selected in the browser.

Use Change team on the API Tokens page to move a token to another context without replacing the key; you can choose to move its existing usage too, which also moves it between quotas. If you leave the team a token is bound to, the token stops working until you change its context.

What is stored

Janus stores a SHA-256 digest of the token plus its first characters for display. The value itself is never written to the database, the logs, or any metric.