Deploy

DeployResource

Methods

create() ->
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
retrieve() ->
get/v5/agentex/deployments/{deployment_id}

Get a deployment by its ID.

list() -> SyncCursorPage[]
get/v5/agentex/deployments

List all deployments with pagination and optional filters.

logs(, ) ->
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
Parameters
deployment_id: str
cursor: Optional[str]

Cursor from previous response's next_cursor field

limit: Optional[int]
(maximum: 500, minimum: 1, default: 100)

Maximum number of log lines to return

Returns
class DeployLogsResponse:

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
deployment_id: str

The deployment ID

has_more:

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

lines: Optional[List[]]

Structured log lines

next_cursor: Optional[str]

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

Request example
200Example

Domain types

class AgentexCloudDeploy: ...
class AgentexCloudDeployEvent: ...

Slim event representation for the API response.

class DeployLogsResponse: ...

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