What is Agentic Booking?
Domain semantics for AI agent discovery and booking in hospitality.
Agentic Booking extends A2A (Agent-to-Agent) and UCP (Universal Commerce Protocol) for the hospitality vertical. It defines what AI agents need to understand and book places to eat, drink, stay, and play.
The problem
AI agents are getting good at conversation. But when it comes to actually doing things—booking a hotel, reserving a table, finding the right venue—they hit a wall.
Every venue has different systems. Different APIs. Different ways of describing what they offer. An agent that can book one hotel can't necessarily book another.
The solution
A shared vocabulary. Open specs that define:
What venues publish
So agents can understand them
How bookings work
So agents can make them
Who to trust
So agents know which venues are legitimate
The six building blocks
Venue
What a hospitality venue publishes to be understood by AI agents.
Bookable
The base pattern for anything that can be reserved.
Folio
The guest account. Payments, charges, refunds.
Stay
The booking lifecycle from request to checkout.
Curator
Discovery and trust. How agents find and verify venues.
Connect
Real-time integration. How venue systems expose live data.
The architecture
Three principles shape this design:
Venues own identity
Every venue controls its own record—hosted on its domain, signed with its keys. DIDs let venues prove who they are without depending on any platform.
Guests own data
Booking history, preferences, and credentials belong to the guest. Stored in their wallet, presented with consent, portable across venues and agents.
Curators are transparent
Who endorsed a venue? Why? Verifiable Credentials make trust signals cryptographically provable—not hidden algorithms.
This isn't decentralisation for ideology. It's for data quality. When venues control their records, they keep them current. When guests own their history, it follows them. When trust is transparent, agents can cite their reasoning.
The mechanisms: DIDs for identity, VCs for claims, and Folio for portable financial records.
Built on standards
This isn't a new protocol from scratch. It's an extension layer:
A2A (Agent-to-Agent)
Google's standard for agent communication. Defines how agents discover each other and exchange messages.
UCP (Universal Commerce Protocol)
The commercial transaction layer. Handles payments, lifecycle, and business logic.
We add the booking-specific semantics on top. Venue types, booking patterns, trust hierarchies—the vocabulary agents need for hospitality.
Get involved
This is an open standard. We welcome contributions from venues, technology providers, and anyone building AI agents for hospitality.
- GitHub: AgenticBooking/specs
- Contact: hello@agenticbooking.org
Led by Selfe · 20-22 Wenlock Road, London, N1 7GU, UK