API surfaces
The server API is planned around ingest, rollups, limit windows, pricing, burn-rate forecasts, alert state, and machine/provider metadata.
Integration posture
REST endpoints should expose the same normalized values used by the dashboard. WebSocket streams can support live dashboard updates and external tools that watch current subscription-window status.
Provenance
Every aggregate should be explainable. API responses are expected to preserve whether a value came from local logs, stats cache bootstrap, OAuth limit signals, pricing tables, or derived rollups.