Update an existing agent’s configuration or deploy a new version.
Authentication requires a Pipecat Cloud Private API token.
Generate a Private API key from your Dashboard (Settings > API Keys > Private > Create key) and include it as a Bearer token in the Authorization header.
Name of the agent to update
The container image to use for the agent
"your-username/my-agent:latest"
The type of node to run the agent on. Only arm is supported at this time.
"arm"
The name of the image pull secret set to use
"dockerhub-credentials"
The name of the secret set to use
"my-agent-secrets"
Auto-scaling configuration for the agent
Whether to enable Krisp noise cancellation. Deprecated: Use krispViva instead for the latest Krisp VIVA models.
false
Krisp VIVA noise cancellation configuration. Learn more.
The agent profile to use for resource allocation. Valid values are:
agent-1x: 0.5 vCPU and 1 GB of memory. Best for voice agents.agent-2x: 1 vCPU and 2 GB of memory. Well suited for voice and video agents or voice agents requiring extra processing.agent-3x: 1.5 vCPU and 3 GB of memory. Best for voice and video agents requiring extra processing or multiple video inputs.agent-1x, agent-2x, agent-3x "agent-1x"
Pipecat Cloud provides API keys for some Pipecat services that you can use directly in your applications. Learn more.
false
Agent deployment updated successfully
Name of the agent
The region where the agent is deployed
Whether the latest deployment has passed validation and is ready. For scale-to-zero agents, this is true even when scaled down to zero replicas.
Whether the agent can accept new sessions. True when any pods are ready to handle traffic, or when scaled to zero but healthy (requests will queue and trigger scale-up). During rolling updates, this may be true even if ready is false, as old pods continue serving while new ones validate.
Creation timestamp of the agent
Last update timestamp
ID of the active deployment
Deprecated: Use ready instead. Whether the active deployment is ready. This field is redundant with ready and will be removed in a future version.
Number of active sessions
Details of the current deployment
The agent profile used for resource allocation
Krisp VIVA noise cancellation status