Builders
Building on the infrastructure. Creating agents and integrations that use hospitality data and booking capability.
The job
Builder
Job: Access hospitality data and booking capability for my agent
I'm building something—an AI agent, a travel app, a booking integration. I need reliable data about venues, the ability to check availability, and the capability to complete bookings.
What's broken today
Want to build an agent that can book hotels? Today you'd need to integrate with every hotel chain separately, parse marketing copy of varying quality, and build booking flows for each property management system.
For agent builders:
- No structured data about venues—just marketing websites and PDFs
- Every booking system has different APIs (or no API at all)
- Can't verify the information you're recommending
- Discovery works but completion fails—users get handed off to websites
For the traveller experience:
- Agents can find options but can't book them
- Recommendations based on marketing copy, not verified facts
- No way to know if information is trustworthy
What changes with agents
A standard protocol for hospitality means you build once and connect to everywhere. Rich venue data, real-time availability, and booking completion through a single integration.
From marketing copy to structured data: Every venue has an Echo—a machine-readable identity with verified attributes, vibe descriptors, and evidence-backed claims. Query it like a database, not a brochure.
From custom integrations to standard actions: Check availability, place holds, complete bookings—same operations at every venue. Your agent doesn't need different code for each hotel chain.
From recommendations to transactions: Don't just suggest venues. Actually book them. The full lifecycle—hold, confirm, modify, cancel—through standard protocols.
What builders need
| Need | Why it matters |
|---|---|
| Venue data | Rich, structured information about places |
| Trust signals | Evidence to back recommendations |
| Booking capability | Check availability, hold, book, modify, cancel |
| Standard protocols | Don't reinvent the wheel for every venue |
The specs as building blocks
The Agentic Booking specs define everything builders need:
Bookable
The base pattern for anything that can be reserved. Identity, evidence, fit, actions.
Venue
Hospitality-specific extension. Vibe, attributes, units, neighbourhood.
Stay
Booking lifecycle. States, transitions, holds, modifications.
Folio
Payment semantics. Schedules, policies, refunds.
Curator
Discovery and trust. Stories, verification, recommendations.
A2A + UCP
Underlying protocols. Agent communication and commerce.
Built on standards
Agentic Booking extends existing protocols:
| Protocol | What it provides |
|---|---|
| A2A (Agent-to-Agent) | How agents discover each other and exchange messages |
| UCP (Universal Commerce Protocol) | Commercial transaction layer—payments, lifecycle, business logic |
The specs add hospitality-specific vocabulary on top. Venue types, booking patterns, trust hierarchies.
Getting started
- Read the specs - Understand the data model and protocols
- Get API access - Request credentials for the sandbox
- Build with SDKs - Use provided libraries or call APIs directly
- Test in sandbox - Verify your integration works
- Go live - Connect to production