Skip to main content
The POST /v8/missions endpoint is your entry point for every governed operation on the Praxa Integration Gateway. You submit a goal specification describing what you want the agent to accomplish alongside a resource budget that caps how much work it can do. The gateway records your intent durably, assigns a unique run ID, and hands the mission off to the private policy and broker plane for execution. Because the intake is idempotent, you can safely retry on network failure by re-sending the same Idempotency-Key.
The gateway returns 202 Accepted — not 201 — because recording the intake mission is itself a governed operation. Provider outcomes are verified asynchronously; the response confirms durable receipt, not completion.

Endpoint

Required scope: missions:write Required headers:

Request Body

goalSpec
object
required
The goal specification that describes what the mission should accomplish. The gateway treats this object as opaque and forwards it intact to the policy plane.
resourceBudget
object
required
Hard limits that govern how many resources the mission may consume. All four fields are required. The mission transitions to failed if any limit is reached before the goal is satisfied.

Example Request


Response

Status: 202 Accepted The response body is a MissionProjection object. It reflects the initial state of the mission immediately after intake — the agent has not yet taken any steps.
runId
string (UUID)
required
Globally unique identifier for this mission run. Store this value — you will use it to poll status, stream events, send signals, and cancel.
status
string
required
The mission’s current lifecycle state immediately after intake. On a successful create this is almost always "running" or "waiting".
sequence
integer
required
A monotonically increasing version counter for this projection. Use this value to detect stale reads when polling concurrently.
steps
array
required
List of step summaries recorded so far. Each element contains a stepId (string) and a status (string). This array is empty immediately after mission creation.
Example 202 response

Error Responses

All errors follow RFC 9457 Problem Details. Sensitive fields are redacted before the response leaves the gateway.

SDK Equivalent

Returns: Promise<MissionProjection>