Agent access tokens
An agent access token lets an AI agent manage model servers and machines through Prism’s API. The agent does not get SSH access, provider keys or owner rights. Every action runs under the token and is logged with the token’s label.
Requirements
Section titled “Requirements”- The managed listener is on:
[server] managed_bind(for examplemanaged_bind = "127.0.0.1:18002"). Agent tokens work only there. See Listeners and authentication. - You are the installation owner.
Issue a token
Section titled “Issue a token”-
In the console open Configuration → API keys → Add API key.
-
Enter the agent ID and a label.
-
Under Prism access for an agent (instead of model calls) tick what the agent may do:
Console label Scope Endpoints add and check model servers; change or remove only the ones it added itself operator:providers:write/prism/operator/providers,/providers/remove,/providers/testsee machines and model services operator:compute:readGET /prism/operator/computestart, stop and restart model services operator:compute:controlPOST /prism/operator/compute/servicepower linked cloud machines on and off operator:compute:power/prism/operator/compute/host,/compute/instances,/compute/host/add,/compute/host/remove,/compute/linkask a machine to find its model servers again operator:compute:discoverPOST /prism/operator/compute/discoverEvery agent token can also read its own operations (
GET /prism/operator/operations/{id}). -
Press Add. Prism shows the token (
prism_it_…) once. It expires after 90 days unless you set another expiry.
Such a token cannot call models, and it does not open provider keys, users, the subscription, pairing approval or a machine’s agent allowlist. A token for model calls is a different key; see Connecting clients.
Use the token
Section titled “Use the token”Send it as Authorization: Bearer to the managed address:
curl -s http://127.0.0.1:18002/prism/operator/compute \ -H "Authorization: Bearer $PRISM_OPERATOR_TOKEN"Start a model service:
curl -s http://127.0.0.1:18002/prism/operator/compute/service \ -H "Authorization: Bearer $PRISM_OPERATOR_TOKEN" \ -H 'Content-Type: application/json' \ -d '{"operation_id": "start-qwen-1", "id": "qwen-coder", "action": "start"}'action is start, stop or restart. Each change carries an
operation_id you choose; sending the same operation_id again returns the
same operation instead of running it twice. Host power uses
POST /prism/operator/compute/host with "action": "power_on" or
"power_off".
The agent finds these endpoints in GET /prism/agent-context. The agent
calls them over HTTP; prism mcp --operator does not expose the compute and
provider actions.
Errors
Section titled “Errors”| Answer | Cause |
|---|---|
401 unauthorized |
No token, wrong header, or the token is revoked or expired |
403 |
The token lacks the scope for this endpoint |
403 not_own_connection |
The token tried to change a model server it did not add |
403 corporate_unavailable |
The action needs an active Pro, Teams or Enterprise subscription |
409 busy |
Another operation on the same service is running |
404 not_found |
No model service with that id |
Revoke
Section titled “Revoke”Configuration → API keys, then remove the key.