Skip to content

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.

  • The managed listener is on: [server] managed_bind (for example managed_bind = "127.0.0.1:18002"). Agent tokens work only there. See Listeners and authentication.
  • You are the installation owner.
  1. In the console open Configuration → API keys → Add API key.

  2. Enter the agent ID and a label.

  3. 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/test
    see machines and model services operator:compute:read GET /prism/operator/compute
    start, stop and restart model services operator:compute:control POST /prism/operator/compute/service
    power linked cloud machines on and off operator:compute:power /prism/operator/compute/host, /compute/instances, /compute/host/add, /compute/host/remove, /compute/link
    ask a machine to find its model servers again operator:compute:discover POST /prism/operator/compute/discover

    Every agent token can also read its own operations (GET /prism/operator/operations/{id}).

  4. 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.

Send it as Authorization: Bearer to the managed address:

Terminal window
curl -s http://127.0.0.1:18002/prism/operator/compute \
-H "Authorization: Bearer $PRISM_OPERATOR_TOKEN"

Start a model service:

Terminal window
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.

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

Configuration → API keys, then remove the key.