CONTROL PLANE

REST and WebSocket API

The web experience uses the same public execution surface available to local tools and future hosted clients.

FastifyRESTWebSocketNormalized events

Health and registries

Check service health and read the components registered in the running system.

GET /api/health
GET /api/environments
GET /api/agents
GET /api/evaluators

Run lifecycle

Create a persisted experiment, list run history, and retrieve its normalized record, events, summary, or replay.

POST /api/runs
GET /api/runs
GET /api/runs/:runId
GET /api/runs/:runId/events
GET /api/runs/:runId/replay

Human turns

When a human participant is active, submit a normalized action without bypassing orchestration or the environment validator.

POST /api/runs/:runId/actions

Live stream

The socket sends a run snapshot followed by normalized event packets. Clients should reconnect and recover from REST when needed.

WS /ws/runs/:runId

Secrets and deployment

Provider keys remain in the API process. The browser submits environment IDs, participant assignments, agent IDs, and run configuration—never API credentials.