Product reference

Documentation

Choose a representation and integration path without losing source, freshness, rights, or unknown-state context.

Public interfaces

  • SSR HTML for people and clients that do not execute JavaScript.
  • Markdown alternatives for core venue and documentation pages.
  • Versioned JSON REST endpoints under /api/v1.
  • A protocol-compliant MCP endpoint at /mcp when the runtime reports it enabled.

Start with the contract

Read /openapi.json for the generated REST contract and /docs/capabilities.json for the project-specific capability inventory. Capability entries distinguish code that is implemented, currently enabled, and externally verified.

Shared semantics

  • availability_status remains unknown without real inventory integration.
  • Money is represented as integer minor units; public launch currency is AUD.
  • A quote request never creates a booking and reports booking_status=not_created.
  • Unknown, stale, conflicting, and rights-restricted fields are not silently promoted to facts.