Skip to main content

The live track set, for anyone who is not hydrating a console.

GET 
/api/tracks

GET /api/picture is the heaviest thing this server serves and it is for hydration: one client behaviour, sized for it, and the rule beside it is hydrate once and hold the stream. Somebody integrating wants tracks, and reading the whole picture to get at part of it is the thing that rule exists to stop (CLAUDE.md rules 1 and 2, spec §7).

Observations go in at POST /api/signals. Until this route, nothing read a track back out except the hydration payload.

Responses​

every live track in the workspace