Roadmap
What's done, what's next, what we're considering.
Current state (v0.1)
Venue
Booking Terms
Stay
Curator
Next priorities
Real-time availability
The current specs define what a venue is. They don't yet define how agents query live availability.
Needed: Availability query schema, rate/pricing response format, inventory hold protocol, calendar-based availability windows.
Multi-venue itineraries
People don't book one hotel. They plan trips.
Needed: Itinerary container, sequential booking coordination, partial failure handling, cross-venue payment aggregation.
Guest context
Agents need to pass user context to venues without exposing unnecessary personal data.
Needed: Preference schema, privacy-preserving context passing, repeat guest recognition.
Group bookings
Business travel, weddings, events.
Needed: Group request schema, room block holds, rooming list management, group payment terms.
Considering
Loyalty integration
Dynamic pricing
Add-ons and upsells
Reviews and reputation
Post-stay
What we're not building
These are explicitly out of scope for Agentic Booking:
| Area | Why not |
|---|---|
| Payment processing | That's AP2, Stripe. We define what should be charged when. |
| Discovery infrastructure | We define what Curators publish. We don't build the index. |
| Agent behaviour | We define what venues say. How agents interpret is agent responsibility. |
| Rendering | We define presentation components. How they render is implementation. |
Contributing
If something's missing or wrong, open an issue. Real-world implementation drives the roadmap.