Skip to main content
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 OK

Response fields

Optimistic concurrency control (OCC)

Updates use the version number for optimistic locking:
  1. The client first calls GET to obtain the current version.
  2. The update sends that version in the request body.
  3. The server checks whether the supplied version matches the current value.
  4. On match, the update succeeds and version increments by 1.
  5. On mismatch, the server returns 409 Conflict.
This prevents concurrent updates from overwriting each other.

Errors

See Errors for the full error envelope.

Error response example

Version conflict (409):

Notes

  • version is required; omitting it causes the update to fail.
  • version increments 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, or skills is provided, the supplied array replaces the stored array for that field.
  • When metadata is provided, string values are merged into the stored metadata object and null values delete existing keys.
  • View the change history with GET /api/v1/cloud/agents/{agent_id}/versions.

Agent setup

Create a reusable, versioned agent configuration.