Skip to content

Get capabilities

GET
/v0/capabilities

Returns a summary of supported features and limits.

Capability document

A deployment’s self-description (API spec, “Capability discovery”).

A remote client fetches this from GET /v0/capabilities and caches it; an embedded engine exposes the same document as a constant. SDK gating logic is therefore identical for both backends: check supports or has_profile, and treat a not_supported error as authoritative when the two disagree.

object
features

Named features and whether this deployment supports them. An absent key means unsupported.

object
key
additional properties
boolean
limits

Advisory numeric limits clients may use to pre-validate requests.

object
key
additional properties
integer format: int64
profiles
required

Advertised profiles, each plane/version. All-or-nothing: every required op of an advertised profile is implemented.

Array<string>
protocol_version
required

The protocol generation, currently v0.

string

Unauthorized

HTTP error body used by LoonFS APIs.

object
code
required

Stable machine-readable reason from the ErrorCode registry.

Carried as a string so clients keep working when a newer server introduces a code they do not know; use ErrorCode::parse for typed access.

string
details
One of:
null
feature

For not_supported errors, the capability-document feature key the client should reconcile against.

string | null
message
required

Human-readable error message.

string
request_id

Correlation id the server assigned to the failed request; the same value is sent as the x-request-id response header.

string | null