Alibaba Just Made Hotel Inventory Open Source
Alibaba's travel platform just made a move that most of the hotel industry won't notice for another twelve months.
Fliggy, the travel division of Alibaba Group, launched an open-source travel skill built on the Model Context Protocol standard. It covers flights, hotels, attractions, ground transport. The full stack, from planning through to booking. Any AI agent can now search and book Fliggy's travel inventory without needing a Fliggy account. Plug and play.
A quick definition, because these terms matter. Fliggy is Alibaba's online travel platform. Think of it as China's equivalent of Booking.com or Expedia. It's an OTA, an online travel agent, that aggregates hotel, flight, and attraction inventory and sells it to consumers. Open source, in this context, means they've published the technical tools for anyone to connect to their inventory for free. Any developer can build an AI-powered travel app that searches and books through Fliggy without asking permission or signing a contract. The protocol they used is called MCP (Model Context Protocol), an emerging standard that lets AI agents interact with external services.
Here's the important nuance. Fliggy is itself an OTA. This isn't a direct connection to hotel systems. It's an OTA making its own inventory programmatically accessible to AI agents. The hotels listed on Fliggy are still listed on Fliggy, presumably under the same commercial arrangements. But the *protocol* and the *pattern* are what matter here. Because if an OTA can do this with its inventory, what stops a PMS provider or a connectivity platform from doing exactly the same thing with the hotel's own rates?
During Chinese Spring Festival, AI-processed orders on Fliggy jumped 800%. Attraction ticket bookings went up twenty-four-fold.
"Consumers are moving from using AI just for search to actually using AI to execute tasks." — Dr. Alex Chen, CTO, Fliggy
That quote deserves to sit with you for a moment. Because the implications for hotels are significant.
What the OTAs Should Be Watching
Right now, Fliggy has made its own OTA inventory available through MCP. That's an OTA expanding its reach, not threatening its own model. But follow the thread.
If you strip an online travel agent back to its core value proposition, what are you left with? Consolidated inventory and a booking flow. The discovery layer, the reviews, the comparison shopping... those are features wrapped around a database of available rooms.
The MCP standard doesn't care where the inventory comes from. Today it's Fliggy's OTA database. Tomorrow it could be a PMS provider exposing hotel-set rates directly. An AI agent that can search, compare, and book across multiple sources doesn't need to go through an OTA at all, if the inventory is available elsewhere.
That's the question OTAs should be asking. Not "will Fliggy take our market share?" but "what happens when this protocol is applied to direct hotel inventory?" If the accommodation becomes accessible through standardised protocols without an OTA in the middle, what exactly is the OTA charging fifteen to twenty-five percent for?
They won't disappear. They're too well-capitalised and too embedded in consumer behaviour. But their moat has always been distribution scarcity. This protocol is the first credible crack in that wall.
The Can-Kicking Problem
Before anyone gets excited about a post-OTA world, there's a sober reality. If a connectivity layer or MCP-based protocol replaces the OTA as the distribution mechanism, someone still has to maintain it. The infrastructure, the API standards, the payment flows, the dispute resolution. Someone will charge for that. You might not be paying Booking.com any more, but you'll be paying someone.
The question isn't whether there will be a cost. It's whether that cost is fifteen percent or something dramatically lower. And whether the relationship with the guest sits with the hotel or the intermediary.
The middleman might change. The question is whether the margin changes with it.
What Actually Becomes Valuable
Here's where it gets interesting. If this pattern scales, and hotel inventory becomes accessible to AI agents through standardised protocols, the accommodation becomes the open layer. The booking becomes the least interesting part of the transaction. What surrounds it becomes everything.
Think about what happened to music. Streaming killed exclusive access to songs. Every platform has the same catalogue. So the value moved to playlists, discovery, the experience layer. The winners weren't the ones with the most songs. They were the ones who understood what you wanted to hear next.
Hotels are approaching the same inflection point. If an AI agent can book any property anywhere, then competitive advantage doesn't come from being discoverable. It comes from the experience that no open inventory layer can replicate.
Curation and taste. The difference between "find me a hotel in London" and "find me somewhere that feels like a reward after a tough quarter." That's editorial judgement. That's brand. That's something an algorithm can facilitate but not create.
The pre and post-stay experience. What happens before arrival and after checkout is where differentiation lives. Anticipation, personalisation, the relationship. The booking is just the transaction in the middle.
Bundling intelligence. Not just "here's a room" but "here's the room, the restaurant with the view you'd love, the spa slot before dinner, the walking route for tomorrow morning." That packaging layer is where margin moves when the accommodation layer opens up.
The One Controllable
If you follow this line of reasoning to its conclusion, it leads to the same place it always has. The direct guest relationship is the one controllable a hotel has in the distribution journey. It always has been. But open inventory makes it urgent in a way that years of "book direct" campaigns never quite managed.
Brand strength and guest relationship strength are inherently linked. A hotel with a deep, data-rich relationship with its guests can offer something no AI agent browsing an open inventory can replicate. Context. History. Understanding. The knowledge that this guest always asks for a high floor, prefers a late checkout, and books a table on the first evening.
That's not inventory. That's intelligence. And it lives in the guest data.
The conversation shifts from distribution strategy to data strategy. That's a fundamentally different boardroom discussion.
Which means owning the guest relationship becomes the strategy, not a line item within it. Owning the guest relationship. Having a connected technology stack that makes that data usable. Making sure the doors are open for whatever connectivity layer or AI protocol comes next, because if your systems can't talk to each other, they certainly won't talk to the outside world.
A Term We Need to Define
There's a phrase emerging from this shift that the industry hasn't properly defined yet. Open source inventory. Fliggy has demonstrated the technology at OTA level, but the concept extends far beyond one platform. Most hotel technology conversations aren't even using this language yet.
What does it actually mean for a hotel's inventory to be "open source"?
- Who controls the protocol?
- Who decides the pricing rules?
- What happens to rate parity agreements when anyone can resell inventory through an AI agent?
- How do you maintain brand standards when an AI agent is presenting your property alongside every competitor in a city?
These questions don't have answers yet. But the hotels and technology providers who start asking them now will have a significant advantage over those who discover the questions exist in eighteen months when it's already reshaping their distribution economics.
The Monday Morning Version
For the hotel group reading this and wondering what to actually do about it, the answer is frustratingly simple. Get your stack connected. Make sure your PMS, your CRM, your booking engine, and your guest data platform can talk to each other. Make sure they can talk to the outside world.
Not because you need to plug into Fliggy's MCP skill tomorrow. But because whatever comes next, whether that's an open connectivity layer, an AI booking protocol, or something nobody has built yet, it will require systems that are ready to connect.
The hotels that spent the last decade building walled gardens around disconnected technology are the ones with the most to lose. The ones that invested in interoperability, in APIs, in clean guest data, those are the ones with the doors already open.
When the accommodation becomes open and accessible, the experience becomes the differentiator. The hotels that understand this won't just survive the shift. They'll define it.