zinn-agents

PATCH /v1/agents/{agentId}

Rename an agent, choose its model, or set its monthly AI spend cap.

All zinn-agents endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the agents.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PATCH https://api.zinndigital.com/v1/agents/{agentId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on agents.manage. model empty or zinn-default follows the cheapest verified model; monthly_cap_micros null removes the per-agent cap (the organisation's balance still bounds spend). The gateway refuses a call BEFORE spending once the cap is reached.

Parameters

NameTypeRequiredWhat it is
agentId (path)stringYes—

Request body

NameTypeRequiredWhat it is
namestringNo—
modelstringNo—
monthly_cap_microsintegerNo—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
namestringYes—
appstring<openclaw, hermes, paperclip, activepieces>Yes—
statusstring<provisioning, running, suspended, failed, deleting, deleted>Yes—
status_detailstringYes—
suspend_reasonstring<, standing, customer, ended, staff>Yes—
plan_codestringYes—
paid_bystring<subscription, trial>Yes—
resourcesAgentResourcesYes—
urlstringYes—
modelstringYes—
monthly_cap_microsintegerYes—
spent_period_microsintegerYes—
created_atstringYes—
provisioned_atstringYes—

Errors this endpoint can return

401 · 404