Etraveli Group says its new Flight MCP opens its flight engine to AI agents. Announced on 28 October, it lets developers connect Claude, ChatGPT or any other MCP-compatible client to real-time flight content from a platform that operates in more than 75 markets and powers flights on Booking.com. The detail that matters sits further down. According to PhocusWire, bookings made through it are completed through a payment link to Etraveli’s Flight Network brand. A travel company that wants to take payment in its own environment, or let an agent book on the traveller’s behalf, needs a commercial agreement with Etraveli and its own payment integration.
So the agent shops and a human still pays. Andreas Marquardt, Etraveli’s chief corporate development officer, called MCP “table stakes” and described the company’s earlier ChatGPT plugin as a redirect solution. The new product narrows the gap but keeps the handoff at the point of payment.
Etraveli is not an outlier. Southwest launched a ChatGPT plugin on 6 October, the first US airline to do so. ChatGPT handles discovery and comparison, and the customer finishes the booking on Southwest.com, where payments and reservations remain. Virgin Atlantic’s ChatGPT app, launched earlier this year, follows the same pattern, with discovery in the chat and payment on Virgin’s own site or app.
The exception in the evidence so far is Mindtrip Flights, built with Sabre and PayPal, which lets a traveller complete checkout inside the Mindtrip experience. Sabre supplies the flight technology, PayPal the payment capability. That is one named example of the loop closing, and it took a GDS, a payments company and an AI travel front end working together. It is also in-experience checkout, not necessarily an agent buying without human approval.
The pattern says a good deal about where the difficulty lies. Etraveli, lastminute.com, Kiwi.com and Sabre have all introduced MCP offerings, giving AI agents structured access to flight content and, in Sabre’s case, booking and servicing tools. But access to inventory is not the same as control of the transaction. The harder questions sit around the charge itself: who authorises it when an agent acts, who is the merchant of record, and who refunds the traveller when the agent books the wrong itinerary. Protocols for agent-initiated payments exist, Google’s AP2 among them, but their existence does not mean airline booking flows are using them. Most of the launches above still send the traveller to a checkout the seller controls.
For emerging markets the effect is sharper. This is an inference, not something any of these announcements say, but a handoff to checkout favours whoever already has card acquiring, FX handling and local payment methods in place. An agent can find a fare for a traveller in Lagos or Nairobi in seconds. Whether that traveller can pay with a local card or mobile money, in naira or shillings, at an acceptable approval rate, is settled at the checkout, which still belongs to the OTA or the airline. Content that never reaches a GDS or aggregator is also unlikely to reach the agent, since these servers expose what their operators already hold.
The industry is describing agentic booking as a visibility race, a contest to be seen by the agent. The evidence so far points to a contest over payments. Any seller can make itself visible to an agent. The party that takes the money, carries the liability for a wrong booking and keeps the customer record ends up with the relationship, and today that is still the checkout page. Airlines in Second Speed Markets, where payments are often the weakest point in distribution already, should be asking about settlement before they ask about MCP.
