In August 2026 Google confirmed that agentic hotel booking is in live testing in the United States. Booking Holdings is one of the first partners. Amadeus is the first business-to-business foundational partner for lodging.Skift, 7 August 2026. Read that list again and notice who is not on it.
What the protocols actually are
Three acronyms are worth knowing, and only one of them is currently doing anything in hospitality.
UCP — the Universal Commerce Protocol, announced by Google in January 2026 — is an open standard that lets an AI agent handle discovery, checkout and post-purchase support in one conversation. A merchant declares what it can do in a JSON manifest at /.well-known/ucp, and an agent reads it. No hardcoded integration.Google Developers Blog, Under the Hood: Universal Commerce Protocol.
MCP — the Model Context Protocol — is the plumbing that lets an AI system query a live system such as a property management system or booking engine.
AP2 — the Agent Payments Protocol — handles the payment leg, with cryptographic proof that the traveller consented.
Because the UCP manifest is a public URL, agent-readiness is testable from outside. For any hotel on earth. Without permission. In about two seconds.
So we tested it
We fetched /.well-known/ucp for seventeen domains: twelve hotel groups and brands, five OTAs and travel platforms.
Zero manifests. Fifteen confirmed absent, two unreachable behind bot protection.
Marriott, Hilton, IHG, Hyatt, Accor, Wyndham, Choice, Radisson, Taj, OYO, Lemon Tree, Expedia, Agoda, Tripadvisor — nothing. The same for Agent2Agent discovery endpoints.
Before anyone reads that as an indictment: the honest reason is that the lodging specification does not exist yet. Google's developer page for hotel UCP is a waitlist — "detailed onboarding and specs coming soon". The ten travel brands Google named at Marketing Live in May 2026 are on that waitlist, not shipping endpoints.
Which means, today, there is nothing to be late for. We would rather tell you that than sell you readiness for a standard that has not been published.
What is actually shipping
Hospitality's live agentic layer is MCP, and it is being built by vendors rather than by hotels.
- Apaleo shipped the first property-management-system MCP server in September 2025, with an agent marketplace alongside it.
- Agentic Hospitality released TravelOS in March 2026, connecting existing CRS and PMS systems to AI platforms.
- Simple Booking put MCP connectors into production in June 2026 across more than 7,000 properties in 75 countries.
- Radisson launched a ChatGPT app in July 2026 covering more than 1,000 hotels — but search and compare only, redirecting to its own site to complete the booking.
Meanwhile Marriott's Ask Bonvoy and IHG's conversational search are first-party tools on the chains' own properties. Those are deliberately not open protocols. Marriott is building an AI search where it controls the answer — the opposite strategic bet from publishing a public manifest.
The fork, and why it is not neutral
Here is the part that should concern a mid-market group.
If a property is named by the AI and bookable by the agent, the intermediary is cut out of that transaction. Direct relationship, no commission.
If a property is named but not bookable, the agent still has to complete the transaction somewhere — so it routes through an OTA. The hotel has just paid commission on a booking that AI generated.
If a property is not named at all, it does not exist in that conversation.
So agentic distribution will either reduce intermediary dependency or deepen it, and readiness decides which. There is no neutral outcome.
And the transactional path that exists today runs through Booking Holdings and Amadeus — through intermediaries, not through hotel-owned domains. That is the same pattern that produced OTA dependency the first time, running again, for the same reason: the intermediaries have the engineering teams and the standards seat.
The question worth asking your vendors
A group of fifteen to fifty properties cannot build Ask Bonvoy. So the practical choice is between the open-protocol route — which runs through the property management system, central reservations system and booking engine — and the intermediary route, which is the default if nobody does anything.
That choice is being made right now by vendor roadmaps, and most groups have not been asked.
Four questions worth putting in writing to each supplier:
- Do you have an MCP server today? If so, what can an agent do with it — search only, or transact?
- What is your position on UCP for lodging, and are you on Google's waitlist?
- If an AI agent completes a booking through your system, which channel does it record, and what commission applies?
- Are our rates, availability, room definitions and policies exposed in a machine-readable format today, and to whom?
The fourth is the one that matters most and the one least likely to have been considered.
What we would not do yet
We would not rebuild a marketing strategy around agentic commerce this year. OpenAI stepped back from direct travel transactions in March 2026. The protocols are real but early, and almost no hotel group has a budget line for them.
What is worth doing now costs nothing: find out whether an AI agent could complete a booking with you if it tried, and find out what your vendors intend. Those are questions, not projects.
The measurement we sell answers the first half of the problem — whether you are named. The second half, whether you are reachable, is becoming a separate question with its own answer. Right now almost nobody in hospitality is asking either one.