Skip to main content
An agent team organises tasks as a directed acyclic graph (DAG) that several workers work through. Creation validates duplicate ids, dangling dependencies, self-dependencies and cycles before anything is stored; the graph shape never changes afterwards, only task state moves pending → claimed → done.

Endpoints

Authentication

Authorization: Bearer <api_key> or Authorization: ApiKey <key>. Optional if AGENT_CLOUD_API_KEY is unset. Every row is scoped by principal_id.

Request body

string
required
Team name (non-empty).
array
required
Non-empty task list. Each item has id (optional, t1… by default), title and depends_on (task ids).
For claim: worker (optional, defaults to the current principal id). For complete: result (the task output).

Response

string
Team id (server-generated when omitted).
string
Always agent_team.
string
Team name.
array
Task list with id, title, depends_on, state, claimed_by, etc.
integer
Number of completed tasks.
integer
Total number of tasks.
claim returns 403 when dependencies are unfinished or the task is already claimed; an unknown team is 404; a cycle or dangling dependency is 400; ids owned by another tenant are invisible and unwritable.