Registry API
API reference
The registry API is an HTTP API described by an OpenAPI 3.1 document. The dashboard and the CLI use it. One page per area.
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.
- Public registry2 operations
Search and read public canonical packages without signing in.
- Packages11 operations
Create canonical packages, list and read them, and manage their versions.
- Workspaces11 operations
Create workspaces, update them, roll them back and read their rendered output.
- Home stacks2 operations
Read the stack catalog of installable home stacks.
- Objects3 operations
Upload and download content-addressed objects.
- Assets4 operations
Create, read and update assets and list their versions.
- Organization overview2 operations
Organization statistics and the activity feed the dashboard shows.
- Onboarding2 operations
Put a new user into an organization and name it.
- Administration11 operations
Members, teams, SSO configuration and organization policies.
- Service accounts5 operations
Non-human identities for CI and automation, and their API tokens.
- Webhooks7 operations
Organization-owned endpoints that receive signed event notifications.
- Telemetry4 operations
Ingest telemetry events and read drift, sync and provider-usage series.
- Audit log1 operation
Query the record of who did what to which resource.
- Content scans1 operation
Read the content scan result of a package version.
- AI analysis3 operations
Run and read advisory AI analysis of package versions and ad-hoc assets.