Skip to main content

Mission endpoints

Create a mission

The required data field is a JSON-encoded mission document string. Do not send tasks or team as top-level request properties. Optional top-level fields are prompt, name, status, schedule, deadline, endDate, notifications, and user.
A task in the document requires title and description and can include assignTo, dependsOn, expectations, expectedOutcomes, metrics, maxRetries, maxDuration, retryPolicy, notifications, and sideEffects. team is an array of volatile agent configurations. Quality gates, checkpoints, and delays require a name, at least one afterTasks entry, and at least one blocksTasks entry. Mission resources retain data as a string and include id, name, prompt, status, scheduling fields, qualityThreshold, notifications, executionCount, user, and timestamps.

Update a mission

PATCH /v1/missions/{id} accepts only data, status, name, schedule, deadline, and endDate.

Execute a mission

Mission execution returns JSON rather than an SSE stream:
Poll the created tasks or connect to /v1/events for live progress.

Atomic document endpoints

Task mutation paths identify a task by its title, not its generated task ID. Global checkpoint and delay listings are available at GET /v1/missions/checkpoints and GET /v1/missions/delays.