Concepts
Open Hotel Protocols
The open interface layer that lets agents operate stays end to end.
Last updated
Open Hotel Protocols define a common, machine-readable contract for hotel operations — availability, rates, reservations, and the guest journey — so that any compliant agent or partner system can interoperate without bespoke integrations.
The four surfaces#
| Surface | What it covers |
|---|---|
| Inventory | Room types, attributes, and physical constraints |
| Availability | Bookable windows, restrictions, and rate plans |
| Reservations | The booking lifecycle, from hold to checkout |
| Journey | Guest-facing events an agent can act on mid-stay |
Each surface is versioned independently, and each response can describe itself: an agent that has never seen a property before can fetch the schema, read the constraints, and transact without a human writing a mapping first.
Design principles#
- Open by default. The specification is public; conformance is testable.
- Schema-first. Every payload has a published, fetchable schema.
- Agent-safe. Writes are idempotent and every mutation names its actor.
Tip
Design your integration against the protocol, not against a single vendor. That is the whole point of it being open.