Post agents
Authorizations
JWT Bearer token obtained from authentication. Pass as: Authorization: Bearer
Body
Request body for creating a new agent
Human-readable display name for the agent
2 - 100URL-friendly unique identifier (lowercase alphanumeric and hyphens only)
2 - 64^[a-z0-9-]+$Organization ID that owns this agent (derived from auth if omitted)
^[0-9A-HJKMNP-TV-Z]{26}$Optional email address to provision for this agent
Whether to automatically provision a phone number for this agent
Arbitrary key-value metadata associated with the agent
ID of an existing inbox to associate with this agent. If omitted, a new inbox is created automatically.
^[0-9A-HJKMNP-TV-Z]{26}$Response
OK
Full agent resource representation
Unique identifier of the agent
^[0-9A-HJKMNP-TV-Z]{26}$Organization ID that owns this agent
^[0-9A-HJKMNP-TV-Z]{26}$Human-readable display name
URL-friendly unique identifier
Current lifecycle status
ACTIVE, SUSPENDED, DELETED Prefix of the agent's API key for identification, or null if no key is set
ISO 8601 timestamp of the last API-key rotation, null if never rotated
Arbitrary key-value metadata
Email identities associated with this agent
Phone identities associated with this agent
Timestamp when the agent was created
Timestamp when the agent was last updated
Per-capability readiness summary. Optional for backward compatibility — clients without readiness handling continue to work; clients that branch on it get the delayed-verification gap closed.
