Public event reserve page

A visitor (not a member, no login) reserves a spot at an event from a shared link — org resolved server-side from the event id, IP rate-limited. Standalone page, noindex, no dashboard chrome.

If you are building a front end

Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: POST /events/:id/reserve (public).

Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.

How to turn it on: Per-event link you share (/e/:eventId).
Who can use it: public by design; POST /events/:id/reserve is the rate-limited wall.
The API behind it: POST /events/:id/reserve (public)
Where it lives: /e/:eventId

See it in context

Events & ticketing — the full walkthrough, step by step: Publish an event; your site sells it — registration, check-in, and the follow-up.

Machine-readable

This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.