API Service
Start and stop
The API command manages a local FastAPI process and keeps a pidfile in runtime state. On restart and stop it attempts graceful shutdown first, then falls back to process termination when necessary.
Health and status
Unauthenticated endpoints:
GET /health/liveGET /health/ready
Authenticated examples:
GET /api/statusGET /api/servicesGET /api/node/statusGET /api/observe/stream
Authentication
Most operational endpoints require:
The CLI resolves this token automatically for local control operations.
Major API areas
/api/services/*: service skill supervision/api/skills/*: skill listing, install/update, runtime prepare/activate, uninstall/api/scenarios/*: scenario install, sync, push, uninstall/api/node/*: node status, reliability, role, members, media, Yjs webspaces/api/observe/*: ingest, tail, and SSE stream/api/subnet/*: register, heartbeat, context, nodes, deregister/api/admin/*: drain, shutdown, lifecycle, and core-update orchestration
Notes
/api/sayand/api/io/console/printstill exist, but the code marks them as deprecated in favor of bus-driven flows.- The API server also mounts additional routers for join flows, STT, NLU teacher functions, and external IO webhooks.