Documentation

Deploy

deploy

Methods

Create Deployment ->
AgentexCloudDeploy
post/v5/agentex/deployments

Create a new deployment.

Submits a deployment request. The deployment will:

  1. Parse and merge configuration files
  2. Create a Kubernetes Job running helm install
  3. Wait for deployment completion
  4. Return results
Get Deployment ->
AgentexCloudDeploy
get/v5/agentex/deployments/{deployment_id}

Get a deployment by its ID.

List Deployments -> CursorPage<
AgentexCloudDeploy
>
get/v5/agentex/deployments

List all deployments with pagination and optional filters.

Get Deployment Logs -> { deployment_id, has_more, lines, 1 more... }
get/v5/agentex/deployments/{deployment_id}/logs

Get structured log lines for a deployment with cursor-based pagination.

The CLI can poll this endpoint to stream logs incrementally:

  1. First call: no cursor
  2. Subsequent calls: cursor=next_cursor from the previous response
  3. Stop polling when the deployment reaches a terminal status
path Parameters
deployment_id: string
query Parameters
cursor: string
Optional

Cursor from previous response's next_cursor field

limit: number
Optional
(maximum: 500, minimum: 1, default: 100)

Maximum number of log lines to return

Response fields
deployment_id: string

The deployment ID

has_more: boolean

True if there may be more lines beyond this page (len(lines) == limit).

lines: Array<{ id, message, log_level, 1 more... }>
Optional

Structured log lines

next_cursor: string
Optional

Cursor for the next page. Pass this as the after_id query parameter to get subsequent logs.

Request example
200Example
Delete Deployment ->
AgentexCloudDeploy
delete/v5/agentex/deployments/{deployment_id}

Soft-delete a deployment. Marks it as deleted and triggers K8s resource cleanup.

Domain types

AgentexCloudDeploy = { id, account_id, created_at, 11 more... }
AgentexCloudDeployEvent = { message, reason, timestamp, 1 more... }

Slim event representation for the API response.

DeployLogsResponse = { deployment_id, has_more, lines, 1 more... }

Response containing structured deployment log lines with cursor-based pagination.

The CLI can poll this endpoint to stream logs incrementally:

  1. First call: no after_id
  2. Subsequent calls: after_id=next_cursor from previous response
  3. Stop polling when has_more is False and the deployment reaches a terminal status