Docs / Protocol

Registry v1

The site and JSON API use the same registry/ source data. API files are generated at build time; clients do not execute Astro pages.

Endpoints

GET /api/v1/registry.json
GET /api/v1/index.json
GET /api/v1/plugins/<id>.json
GET /api/v1/plugins/<id>/versions/<version>.json

The root index is a relative URL so the Registry can be mirrored. Open the Registry root ↗

Client version selection

latest_published in the index is not necessarily installable. Clients should read version details, exclude yanked releases, then select the highest compatible SemVer based on allowed channel, app version, Plugin API, and RPC API.

Yanks and caching

Release identity cannot be overwritten. A yank adds a reason and makes a release ineligible for installation. Cache the root and index briefly; clients must recheck mutable yank status and tolerate offline cache usage.

Current state

There are 1 drafts and 8 published plugins. Drafts do not appear in the public index and are not installable.