How it works

The architecture of Agentic Booking.


The six building blocks

Agentic Booking defines six interconnected building blocks:

Building BlockPurpose
VenueWhat a hospitality venue publishes to be understood by AI agents. Profile, evidence, facilities, capabilities.
BookableThe base pattern for anything that can be booked—rooms, tables, tickets, experiences.
FolioThe guest account. What's owed, what's paid, what happens if plans change.
StayThe booking lifecycle. From request through check-in, during the stay, to checkout.
CuratorThe discovery and trust layer. How agents find venues, and know which to trust.
ConnectReal-time integration. How venue systems expose live availability and accept bookings.

How they fit together

0

Discovery

A guest tells their agent what they want. The agent queries Curator for trusted venues matching the request.

0

Evaluation

The agent reads Venue profiles to understand options—facilities, vibe, evidence of claims.

0

Booking

The agent uses Bookable to check availability and make a reservation.

0

Payment

Folio handles the money—deposits, balance, charges during the stay.

0

Lifecycle

Stay manages the booking from confirmation through checkout and beyond.

Extension model

Each building block extends the A2A Agent Card:

Standard A2A

Identity, capabilities, and communication endpoints from the base spec.

Venue extension

Profile, facilities, vibe, evidence—everything that describes the property.

Bookable extension

Inventory, availability, rates—everything needed to make a reservation.

Curator endorsements

Trust signals from DMOs, portfolios, and editorial curators.

Connect integration

Real-time APIs to the venue's property management system.

The extensions are additive—a venue can support any combination based on what it offers.