Google Hotels: “Where should I stay?”
A guest can compare hotels and follow a booking link to a hotel or partner. That’s useful distribution. The hotel supplies its rates and booking destination through a supported route. The link itself doesn’t tell my own assistant how to add a birthday package or come back next week and arrange a car. How Google’s hotel booking links work.
Meta’s Muse and Cloudbeds: “I already use this assistant.”
Muse is Meta’s personal AI agent. Cloudbeds announced an integration for participating hotels: Muse would access live rates and availability and use the Cloudbeds Booking Engine. For a hotel on that system, it’s a way to reach people already using Muse. Cloudbeds said its US rollout was scheduled to start in the first quarter of 2027. I didn’t test it. Mews, the hotel software company, is a different business from Muse.
Glass Lantern: “I’m bringing my own AI.”
The hotel puts tools on the site it already has. If my AI can use them, it can ask for the room, the cake and the total. If I want to see the view, speak to the hotel or pay myself, the same stay is there on screen. There’s no separate Glass Lantern app for me to join. In return, the hotel has to do the integration work and support guests whose agents can’t finish.
That last part matters. In my Gemini test it found the hotel and eventually got the price, but it didn’t produce a checkout link. Codex did. I wouldn’t tell a hotel this works with every AI today. I would ask: when a guest’s AI stops, how much of the conversation can the guest keep?