Registry API
API reference
The registry is an HTTP API (Hono). The dashboard and the CLI use it. One page per area.
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.
- Public catalog5 operations
Read public packages and published workspaces without signing in.
- Sign-in and tokens7 operations
Device login, OIDC sign-in, CI tokens and the caller’s identity.
- Registry objects5 operations
Content-addressed storage for package asset content, by sha256 hash.
- Packages5 operations
Draft, publish, read and change the visibility of package versions.
- Workspaces8 operations
Workspace revisions, published workspaces, forks and drift reports.
- Approvals and audit3 operations
Package approvals by registry admins, and the audit log of every action.
- Webhooks6 operations
Register signed callbacks, test them, and redeliver failed deliveries.
- AI review5 operations
Advisory reviews of package versions and workspaces, with a follow-up chat.
- Telemetry2 operations
Privacy-checked telemetry intake and the dashboard aggregate.
- Role mappings3 operations
Map SSO groups to principal roles.
- Health and spec3 operations
Liveness, a readiness check against the database, and the live OpenAPI document.