Skip to main content
PATCH

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

Workspace ID.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

agentId
string
required

Agent ID. Accepts the canonical agent_… form or the external_id:<value> form.

Example:

"agent_01HXKD2E5NQM3T9AYWCFMGWT9Y"

id
string
required

Variation ID. Accepts the canonical agentvar_… form or the external_id:<value> form.

Example:

"agentvar_01HXKD2E5NQM3T9AYWCF32BSPP"

Body

application/json

Update agent variation request

metadata
object

UpdateResourceMetadata contains the user-provided fields for updating a workspace-scoped resource. Read-only fields (id, account_id, workspace_id, profile_id, created_at) are excluded since they are set by the server.

spec
object

AgentVariationSpec defines the complete operational configuration for a variation, including assignments. Reads always populate both assignment lists, even when include_info is false. Create and update validate and persist the configuration atomically: any invalid target or cascade rejects the entire request. Targets must belong to the variation's workspace and pass the same eligibility checks as the dedicated add methods.

updateMask
string<field-mask>

Fields to update. Assignment lists are replaced as a whole, never merged. Select spec.assignments or spec.memory_layer_assignments to replace/clear one list. Selecting spec replaces the entire spec (including omitted lists);

  • replaces all mutable fields. Element/index paths are not supported. Without a mask, infer paths from non-empty fields: non-empty assignment lists replace existing lists, while omitted/empty lists remain unchanged. To clear a list, explicitly include its path in the mask.

Response

OK

AgentVariation resource

metadata
object
required

Resource metadata

spec
object
required

Variation specification

info
object
required

Read-only summary information