The wire, as schemas

JSON Schemas (2020-12) for every wire payload, published here at permanent URLs and synced from the spec repository at every deploy. They are meant to be vendored — copied into your implementation like the builder registry — and never fetched at request time.

The prose specification is normative; the schemas are normative for JSON shape only — field names, types, required-ness, enums, formats. On any conflict the prose wins and the schema is defective: fix the schema, never fork it.

/schemas/v1/listing.schema.json

OpenYacht Listing

Full listing payload as served at GET /openyacht/v1/listings/{uuid} and inside /listings collection responses.

/schemas/v1/collection.schema.json

OpenYacht Listings Collection

Response envelope of GET /openyacht/v1/listings: a page of listings and tombstones plus sync metadata.

/schemas/v1/tombstone.schema.json

OpenYacht Tombstone

Marker for a listing that became invisible to the requesting partner (withdrawn, sold, or unshared), delivered in /listings sync results and subscription pushes.

/schemas/v1/error.schema.json

OpenYacht Error

Error envelope for all federation endpoints.

/schemas/v1/well-known.schema.json

OpenYacht Discovery Document

The document every node serves at GET /.well-known/openyacht: identity, keys, and endpoint map.

/schemas/v1/capabilities.schema.json

OpenYacht Capabilities

Response of unsigned GET /openyacht/v1/capabilities.

Registries

Fixed vocabularies both authorities and consumers validate against. Versioned like tzdata: vendor a copy, update out of band. Additions via pull request to the spec repository.

/registry/builders.json — builder vocabulary · 2026.08.0 · 358 entries
/registry/categories.json — category vocabulary · 2026.08.0 · 40 entries
/registry/destinations.json — charter destination vocabulary · 2026.08.0 · 156 entries

The federation API is also described as an OpenAPI 3.1 document — like the schemas, normative for JSON shape only.