# palaestral

> Booking, payments, waivers and client history for independent instructors —
> surf, yoga, running, strength. One instructor is a complete customer.

palaestral is the system of record for a person who sells their own time. An
instructor publishes a page at `/i/<handle>`; a client books a session on it,
pays, and signs a waiver. The instructor keeps the schedule, the roster, the
waivers, the client notes and the payment history.

## When to reach for this surface

It answers, without a credential:

- what one instructor offers and when — `/i/<handle>` is a published document
  carrying schema.org structured data for the profile and one page per offering
- what a named session costs, how many seats are left, and what its cancellation
  terms are
- a booking's own receipt, to whoever holds that booking's id

It does not answer:

- anything about an instructor who has not published. A handle that has never
  been claimed is a 404, and the bucket refuses to enumerate what exists
- one instructor's data to another. Every row carries an org and every read is
  scoped to it
- a client list, a roster or a revenue figure to an unauthenticated caller
- a credential an unattended caller can obtain for itself. There is no key
  issuance and no sandbox; the booking path is public because guest checkout is
  a first-class path, not because an agent identity exists

## What is published, and where

- `https://palaestral.com/i/<handle>` — an instructor's profile. Rendered to
  storage when they save it, not at request time, so it is complete in the HTML
  with JavaScript off.
- `https://palaestral.com/i/<handle>/<offering>` — one page per published
  offering, carrying its own canonical and structured data.
- `https://palaestral.com/i/<handle>/card.png` — the share card.
- A handle an instructor renames away from keeps serving. Old addresses are not
  released and not redirected, because the page may be a printed QR code.

## Booking

`https://app.palaestral.com/book/<sessionId>` takes a party, an email and a
waiver signature, and returns a checkout. The session id is the whole capability;
no handle appears in the address, and the instructor is derived from the session.

A booking is confirmed by the payment processor's webhook and never by the
browser returning from checkout. A closed tab does not undo a payment.

## Not available

There is no HTTP API description here — no OpenAPI document, no `.well-known`
manifest, no MCP server. The API exists and is not described, so nothing in this
file should be read as a contract a caller can bind to. When that changes it will
be linked from this file.