API reference
Generated from the capability registry. Not written by hand, and therefore unable to drift.
The reference lands with the REST facade. This page describes how it is produced, so you know what you will be reading.
Generated, not written
Every reference page is generated at build time from the capability registry itself — the same declaration the server reads to decide what exists, who may call it, and what parameters it takes. Nobody edits these pages. A capability that is removed disappears from this reference on the next build, and a build whose generated reference differs from the committed one fails.
That is not tidiness. A reference maintained by hand drifts, and a drifted reference is worse than no reference: it is a documented promise the server does not keep.
What appears, and what never does
Only capabilities that are read, or the propose half of a proposal pair, and only those addressed
to tenants. A write capability is not listed anywhere, because it is not directly callable — it is
reached through the proposal it belongs to, and listing it would invite a client to try.
Capabilities restricted to a plan are listed and marked as such. Gating happens when a connection is authorised, not when you read a page: you should be able to see what you would get before you buy it.