Mission control API
Mission control provides a real-time view of your agent fleet. Use these endpoints to visualize agent relationships, trace execution activity, attribute costs per agent, and track talent bookings.All mission control endpoints require bearer token (API key) authentication. The fleet graph and traces endpoints also require a
userId query parameter. The web proxy uses session authentication and resolves the user ID from the session before forwarding to these endpoints. The fleet graph and traces endpoints return safe default responses for unauthenticated requests instead of an error.Fleet graph
role and positional data for graph layout. Edges use from/to fields with a strength value indicating relationship weight.
Authentication
Requires bearer token authentication.Query parameters
Response
Node object
The
type field was renamed to role and now uses the values orchestrator, specialist, and worker. The monitor role is no longer returned by this endpoint.Edge object
The
source and target fields were renamed to from and to. The type field on edges was replaced by strength.Response metadata
Errors
Unauthenticated requests return a200 response with default empty data (see above) instead of an error.
Execution traces
Authentication
Requires bearer token authentication.Query parameters
Response
Trace object
The response is capped at 20 traces, sorted from most recent to oldest.
Errors
Unauthenticated requests return a200 response with an empty array [] instead of an error.
Cost attribution
Authentication
Requires session authentication.Response
Response fields
Errors
Unauthenticated requests return a200 response with { costs: [] } instead of an error.
Talent bookings
Authentication
Requires session authentication.Response
Response fields
Errors
Unauthenticated requests return a200 response with { bookings: [] } instead of an error.