Registry API

Telemetry

Privacy-checked telemetry intake and the dashboard aggregate.

Every event is validated before it is stored, and events carrying forbidden fields (raw prompts, raw outputs, file content, exact paths, diffs, usernames, emails, tokens) are refused. The CLI sends none; workspace manifests default telemetry to off.

Operations

Telemetry operations
Request	What it does
POST /v1/telemetry/events	Ingest telemetry eventsin spec
GET /v1/telemetry/dashboard	Get telemetry dashboardin spec

Operations are the routes the server registers; this site checks its list against the route definitions. Operations marked “in spec” are also described in the committed OpenAPI file (apps/api/openapi.json), which does not yet cover every route. Only the public catalog and the health check work without a token.

More areas

All areas →

01
Public catalog
Read public packages and published workspaces without signing in.
02
Sign-in and tokens
Device login, OIDC sign-in, CI tokens and the caller’s identity.
03
Registry objects
Content-addressed storage for package asset content, by sha256 hash.

Operations

More areas

Public catalog

Sign-in and tokens

Registry objects