Registry API
Telemetry
Ingest CLI telemetry events and read sync, adoption, provider, drift and failure aggregates.
The CLI posts anonymized telemetry events here after pull, sync, diff and push unless telemetry is turned off. The read operations power the dashboard’s telemetry views.
Operations
| Request | What it does |
|---|---|
| POST /telemetry/events | Ingest a batch of telemetry events |
| GET /telemetry/syncs | Sync activity |
| GET /telemetry/adoption | Package adoption |
| GET /telemetry/providers | Provider usage |
| GET /telemetry/drift | Drift summary |
| GET /telemetry/failures | Failure summary |
Paths come from the OpenAPI document that the API exports from its route definitions (CI fails if it is stale); this site checks its list against that file. The public registry search and package reads and the health checks work anonymously; most other operations need a signed-in session or an API key.
More areas
All areas →- 01
Public registry and blobs
Anonymous search and package pages, plus content-addressed blob storage.
- 02
Packages
Create packages, publish immutable versions, manage assets, approvals, render previews and reviews.
- 03
Workspaces
Workspace desired state: targets, revisions, the manifest the CLI pulls, overrides and policies.