Lodging & Accommodation — NAICS 721, villa & short-stay sub-niche
The villa & short-stay lodging rail
The Booking record (schema.org Offer/Reservation grain), villa/short-stay Property inventory, night-audit reports, and guest folios — one substrate, two plies (data face + headless Booking/PMS face). Anonymous sandbox is the floor; every sandbox record is labeled example data (simulated — never a real property, booking, guest, or market rate).
What answers today, keyless
Every claim below is a probe, not an adjective. The machine faces are generated from one manifest — docs cannot drift because docs render from it.
- GET /bookings — keyless first value (typed OK envelope)
- GET /properties — the short-stay inventory grain (labeled demo units)
- GET /night-audit-reports — the typed operational artifact (the sector wedge)
- GET /folios — guest folio / guest-ledger records
- agents.json — the card
- openapi.json — the contract (OpenAPI 3.1, live-only)
- mcp — the MCP door (streamable-http; tool names = operationIds)
- icp.json — the G2 coordinates
- substrate.json — the G3 APIProduct instance
- pricing — the rate card (402-shaped stub; nothing bills)
- llms.txt — the agent docs
- verify — runnable public-contract probes
No payment door is mounted at wave zero — the 402 boundary is a labeled stub; nothing bills, nothing is charged, and no terms bind the rate card.
One definition, every face
The quartet, the branching Booking collection, the headless Booking/PMS doors, the MCP door, and the offer boundary are generated from the same frozen manifest.
The branching Booking collection
Typed OK | EMPTY | BLOCKED | OFFER on one pathname — /bookings, filterable by status and property, with record detail by id.
Two plies, one definition
Read the collections (data face) or operate them as a Booking/PMS system of record — createBooking, cancelBooking, runNightAudit land in the disclosed ephemeral workspace. Same envelopes, same rate rows.
Labeled example data, in-band
Every sandbox record carries example: true, a 952 demo id, and @example.com parties — simulated, never a real property, booking, guest, or market rate.
A typed rate card, honestly stubbed
One rate row per served operation, priced from zero or carrying a free quota. The 402 OFFER boundary is real and typed; no billing occurs and no terms bind it.
sandbox
Start with the anonymous floor
No key, no account, no conversation — the sandbox is the universal floor. Example data is labeled in-band on every record.