Skip to main content
An automation token lets a program act on your workspace the way you do in the dashboard: pair a connector, publish a model, create an API key, read usage. You mint it in Settings, choose exactly what it may do, and it expires on a date you pick. Hand it to a coding agent such as Claude Code or Codex, a CI job, or a script, and that program can run the whole setup unattended. It is not an API key. An API key (sk-tok-…) lets a client call your models. An automation token (at-tok-…) lets a program manage the workspace, and it can never call a model with it. The two never cross.
Automation tokens act only on your own workspace. They can never change your password or email, show or share an API key, rotate a connector’s token, read stored prompts, change request logging, or create other automation tokens. Those stay behind a signed-in dashboard session.

​
Create a token

Only a workspace admin can create, list, or revoke automation tokens.
1

Open Settings

In the dashboard, open Settings and scroll to Automation tokens. Click Create token.
2

Name it after what will hold it

Use a name you will recognize in the token list and on the rows it creates, for example claude-code on my laptop or ci-deploy.
3

Pick a preset or choose scopes

Setup is the right preset for an agent that installs the connector and gets your model callable. Read-only suits monitoring. Full grants every scope. Tick individual scopes for anything else. See Scopes below.
4

Pick an expiry

Every token expires. Choose 1 hour for a one-off setup run, longer for a standing job. The maximum is 1 year.
5

Copy the token once

The token is shown exactly once. Copy it into the program’s secret store or a shell variable. If you lose it, Regenerate it from the list; the old value stops working at once.

​
Scopes

A scope is resource:verb. A write scope includes the matching read. Nothing includes keys:rotate or models:reroute. A call outside the token’s scopes returns 403 with the missing scope named in the error, so a program can tell you exactly which grant it lacks.

​
Use a token

Send it as a Bearer token to the dashboard host, not the API host. Every management call lives under https://tokios.com/account/.
For the full list of calls and the order an unattended setup makes them in, see Let a coding agent set up Tokios for you.

​
Hand it to an agent

Create a token with the Setup preset and a 1-hour expiry, then start your agent on the machine that runs your model and send it this prompt:
Set TOKIOS_TOKEN in the shell before you start the agent so the secret never appears in the conversation. The guide page tells the agent everything else.

​
Manage tokens

Each row in Settings shows the token’s scopes, fingerprint, expiry, and when and from which IP address it was last used.
  • Regenerate replaces the secret. The old value stops working immediately and the new one is shown once.
  • Revoke stops the token for good. Create a new one to replace it.
  • Delete removes a revoked or expired token from the list.
Changing or resetting your password revokes every token you created. A token minted from a stolen session stops working as soon as you recover your account, and any standing job needs a new token afterwards. Rows an automation token created carry a via token badge on the Connectors, Models, and Keys tabs, so you can always tell what a program did. The badge stays after the token is deleted.

​
Keep tokens safe

  • Scope narrowly. A Setup token that has finished its job should be revoked, not kept.
  • Expire soon. Use 1 hour for interactive agent sessions. A long expiry belongs only to a standing job in a secret store.
  • Keep it out of transcripts. Read it from a shell variable; never paste it into a chat with the agent.
  • Watch the badge and the last-used column. If a token was used from an address you do not recognize, revoke it.
  • Know what a minted key means. A token with keys:write can create an API key, and that key keeps working after the token expires. Someone who steals a 1-hour Setup token can mint a key with no expiry and call your models until you notice. After any agent run, open the Keys tab, look for rows marked via token, and revoke any you did not expect.
  • Grant models:reroute only when you need it. Moving, renaming, or deleting an existing model changes which machine receives its traffic. A token that can also pair connectors could pair a machine its holder controls and move your model there. Setup never needs it: it creates models but never moves them.
  • Expect a shared address to share a lockout. After 8 failed token attempts from one IP address, every token from that address is refused with 429 for 6 minutes, valid ones included. Agents behind the same office network, NAT gateway, or CI runner pool share that lockout. If one client keeps sending a bad token, stop or fix it instead of letting it retry in a loop.

Agent-driven setup

The step-by-step procedure an agent follows with a Setup token.

API keys

The keys your clients use to call your models.