Registry API
Telemetry
Ingest telemetry events and read drift, sync and provider-usage series.
The CLI sends batches of telemetry events here. Events carry operational metadata only; fields that could hold prompts, code, paths, credentials or personal data are rejected.
The read operations return the time series the dashboard’s telemetry pages chart.
Operations
| Request | What it does |
|---|---|
| POST /api/v1/telemetry/events | Batch ingest telemetry events |
| GET /api/v1/telemetry/drift-trend | Drift time series |
| GET /api/v1/telemetry/provider-usage | Provider usage stats |
| GET /api/v1/telemetry/sync-activity | Sync time series |
Paths and summaries come from apps/api/openapi.json, which CI regenerates from the route definitions; this site checks its list against that file. Only the Public operations work without a token; everything else needs a signed-in session or an API token.