The door stays shut
Airbnb is unlikely to allow outside AI agents — Meta’s Muse named specifically — to complete bookings on its platform, chief executive Brian Chesky told Nikkei Asia in remarks published on 3 October. His stated reason is that the company wants to keep its direct relationship with the people who book.
“Planning travel is entertainment,” Chesky said — the argument being that the browsing, comparing and imagining is the product, not an inefficiency to be removed by delegating it to software.
This is the first clear no from a major consumer marketplace since agentic shopping started shipping. It sits directly against the other posture available: open the checkout and let whatever agent arrives transact.
Not an anti-AI position
It would be a mistake to read this as caution about AI. Airbnb added its own AI-powered property search in its autumn product update, letting users search by text or voice prompt with filters that assemble themselves from what the user asks for.
And at Skift Global Forum on 28 September, Chesky committed to launching an Airbnb AI agent in 2027, calling it the most important product the company has ever built. He also said he wants other companies to publish SDKs that would let Airbnb design its own interface inside their chatbots, rather than having agents drive its site through browser automation.
That last point is the whole position in one sentence. Airbnb is not refusing agents. It is refusing to be scraped by them.
What is actually at stake
If an agent books the stay, the agent owns the customer. The platform becomes inventory: a price and an availability window queried by software, with no homepage, no recommendations, no cross-sell and no brand. Hotels learned this from the online travel agencies two decades ago, and the travel industry has not forgotten the lesson.
The counter-pressure is that consumers may not care who owns the relationship. If an assistant that already holds your calendar and your card can book a trip in one instruction, the platform that refuses it is adding friction the user did not ask for.
The test is whether a refusal is enforceable. Agents that cannot transact through an API can still drive a browser, which is why Chesky’s SDK request matters more than his refusal: he is asking for a negotiated interface precisely because the ungoverned one already exists. What to watch is whether Airbnb’s own 2027 agent arrives before someone else’s agent makes the question moot.
