If you don't have your own interface for AI agents, they will only find you through someone else. Since this year, that is no longer theory. The large travel platforms are building their access points for agents right now, and each one builds them for its own product.

For a specialty tour operator, this is good news and uncomfortable news at once. Good, because the market is settling how agents will talk to suppliers. Uncomfortable, because the big platforms built their access for a kind of product that tour operators don't sell.

What is emerging

An AI agent is a program that searches, compares and recommends on someone's behalf. To work with a supplier, it needs an interface it can operate on its own. The standard for this is the Model Context Protocol, MCP for short. Think of it as a power socket: the supplier decides which tools an agent may use, such as "search accommodation" or "check price", and the agent calls them directly. Nobody fills in a search form anymore.

2025
Sabre opens its MCP server in September
80+
partners use Sabre's MCP services in pilot or production (company figure, November 2026)
May 2026
Expedia announces an MCP server for B2B partners

Booking.com offers an MCP server for approved partners and affiliates. It searches accommodation and flights with live availability and pricing. According to its documentation, placing a booking is not part of it yet. In May, Expedia announced its own server for B2B partners, designed to give agents direct access to its inventory. Sabre is furthest along. Its server has been running since September 2025, and in November it added a connection to a major AI assistant.

Built for products you search

All three follow the same pattern. They open up an inventory of standardised units: a room, a seat, a rental car. Each unit has a date, a price and an availability the system knows within milliseconds. The agent sends a search and gets a list back.

A specialty tour operator sells something else. A twelve-day round trip through Patagonia is made of components: lodges with allotments, a guide with their own calendar, transfers priced by group size, and a seasonal rate that jumps between low and high season. Whether this trip can run in March for four people in the comfort variant is not stored in any database. The answer only emerges from the combination, and for some components someone has to check with the local partner.

"You can search for a hotel room. A round trip is something you have to be able to request."

That is the difference. An interface that only searches returns either nothing or something wrong for a tour programme: a brochure price without the season, an availability nobody has checked. For an agent, both are worse than no answer, because it keeps working with them.

What a tour operator's interface has to answer

Opening your trips to agents takes clean answers to three questions.

  • What is the trip? This means the structure, not the brochure copy: which components, which variants, what minimum group size, what is fixed and what can be swapped.
  • What does it cost, for whom and when? You need a price that knows season, group size and variant, calculated by the same system that writes the quote.
  • What is binding? The most honest answer is sometimes "on request". An agent has to be able to tell whether a service is confirmed or whether the operator still needs to clear it with the partner.

The third question decides trust. That is why Voyager AI follows a simple rule: no agent confirms a service before the supplier has answered. An interface that confirms faster than reality allows sells a trip today and loses the guest tomorrow.

No interface means being found through others

An operator who does nothing does not disappear overnight. Its trips keep showing up, but in someone else's version: as a single hotel on a platform, as a text snippet in an AI answer, as a component sold by an intermediary. The agent finds the lodge in Patagonia. It doesn't find the trip around it, and that composition is exactly what the guest would pay for.

This is the real shift. The big platforms make standard products easy for agents to reach. The easier the standard part is to get, the more a specialty operator's value depends on what cannot be standardised. And the more it matters that exactly this part becomes machine-readable.

Little revenue comes through this route yet: Booking.com says well under one percent of its room nights come from AI assistant referrals. Even so, an interface is better built before the traffic arrives than after. If you want agents to find you in 2027, you need your programme in data form now.

What follows

The first step is unglamorous. Before any agent can send a request, the trips have to exist in structured form: components, seasonal prices, rules, the source of every availability. At many of the 800 owner-managed specialty tour operators in the DACH region, this knowledge sits in brochure PDFs, in spreadsheets and in the owner's head.

This is where we come in. The platform is live (web and Android). The complete 7-agent workflow can be demonstrated end to end. Productive today are the inquiry pipeline, itinerary composition with pricing and margin calculation, and customer management on a multi-tenant white-label foundation. Supplier integration and automated customer communication are the next stages. For operators who don't want to transfer their programme themselves, we are working on done-for-you services that turn tour programmes into structured data.

There is a second reason to start now. A programme that exists as structure, rather than only in one person's memory, can also be handed over. For any company whose succession is still open, the same work pays off twice.

The big platforms' doors are open. For a hotel room, that's enough. If you compose trips, you have to build your own, and its foundation is a programme a machine can read.