POST /api/v1/cloud/agents/{agent_id}
Updates the configuration of the specified Agent. Uses optimistic concurrency control (OCC); the request body must include the current version.
Headers
Path parameters
Request body
Example request
Example response
HTTP 200 OKResponse fields
Optimistic concurrency control (OCC)
Updates use the version number for optimistic locking:- The client first calls
GETto obtain the currentversion. - The update sends that
versionin the request body. - The server checks whether the supplied
versionmatches the current value. - On match, the update succeeds and
versionincrements by 1. - On mismatch, the server returns
409 Conflict.
Errors
See Errors for the full error envelope.
Error response example
Version conflict (409):Notes
versionis required; omitting it causes the update to fail.versionincrements on each successful update.- Updates use merge semantics: optional fields not included in the request body retain their current values. Only explicitly provided fields are updated.
- When
tools,mcp_servers, orskillsis provided, the supplied array replaces the stored array for that field. - When
metadatais provided, string values are merged into the stored metadata object andnullvalues delete existing keys. - View the change history with
GET /api/v1/cloud/agents/{agent_id}/versions.
Related
Agent setup
Create a reusable, versioned agent configuration.