What good travel feels like
Imagine your flight is delayed by four hours. Not cancelled — just delayed, but enough to miss your connection and arrive at your destination too late for the evening activity you booked months ago. In today's world, you spend those four hours on hold. One call to the airline. Another to the hotel to push the check-in. Another to the tour operator to ask about a refund. Another to the activity provider who has no record of your name because you booked through a third party.
Now imagine that none of those calls happen. The delay is registered. The booking adjusts. Your hotel is notified. The activity provider receives a rescheduling request. Your phone shows a single updated itinerary. You sit at the gate and read.
That second experience is not science fiction. It is what travel looks like when the whole industry shares a common language — when a hotel, an airline, an activity provider, and the AI agent managing your trip can all read the same booking record and act on it together.
That common language now exists. It is called the Activity Travel Protocol.
Why the industry never had this before
The travel industry is not short of technology. What it has always lacked is interoperability — the ability for different systems, run by different companies in different countries, to share a single coherent picture of a booking.
Airlines solved their slice of this decades ago. Hotels made progress with shared data schemas. But activities — the ski schools, the local guides, the cultural experiences, the transfers, the things that make a destination worth visiting — were never part of any common standard. And no standard ever covered the complete journey: from the moment a traveller expresses an interest to the moment they return home safely.
The arrival of AI agents has made this gap urgent. AI travel assistants are already in market. They can search. They can recommend. They can, in simple cases, book. But when the itinerary becomes complex — multiple suppliers, multiple jurisdictions, real-time disruption — the AI hits a wall. Not because the AI is not capable enough. Because the infrastructure behind it was never built for this.
The question the industry has been avoiding is simple: who builds the shared foundation? Not a feature. Not an API. A genuine open standard — neutral, governed by no single commercial interest, available to every party in the chain on equal terms.
What the Activity Travel Protocol is
The Activity Travel Protocol is an open standard for the complete travel booking lifecycle. Every party in a booking — hotel, activity supplier, transport operator, OTA, AI agent, traveller — works from a shared runtime record called the Booking Object. It tracks the state of the booking, who holds responsibility for the traveller at each moment, and what every AI agent in the chain is and is not permitted to do.
When something changes — a flight delay, a supplier cancellation, a traveller who cannot be reached — the protocol propagates the change across every affected party simultaneously. No one is waiting for a phone call. No one is working from a different version of the truth.
It is built on four layers: identity and trust, discovery and capability, workflow, and the developer SDK. The full specification is published and live. The licence is Apache 2.0 — open governance, no single owner, free for any company to implement.
The protocol is not competing with existing standards. NDC for airlines and OpenTravel for hotel data continue to do what they do. The Activity Travel Protocol is the layer that connects them — and extends the picture to cover everything those standards were never designed to handle.
What interoperability means in practice
| For… | Today | With the Activity Travel Protocol |
|---|---|---|
| Travellers | Stranded at a gate, calling suppliers who cannot see each other. Personally managing every change across a chain that was never designed to talk. | One booking record, shared across every supplier in real time. When something changes, the chain adjusts. The traveller is informed, not managing. |
| Hotels and activity suppliers | Separate systems, separate APIs, separate conversations with every distribution partner. Coordination by phone and email when things go wrong. | One structured profile, readable by every platform that implements the protocol. Disruption notifications arrive automatically. No manual coordination. |
| OTAs and platforms | Custom integrations for every supplier category, in every market. Growing maintenance burden as the activity catalogue expands. | One protocol integration, every supplier in the network. AI-powered itinerary assembly without rebuilding the supplier layer from scratch. |
| Regulators | Liability chains reconstructed after the fact from email threads and PDF contracts. No real-time record of who was responsible for a traveller. | A timestamped, machine-readable duty of care record in every booking. Accountability is maintained in real time, not reconstructed after an incident. |
What interoperability actually changes
Interoperability is not a technical achievement. It is a commercial and human one.
For travellers, it means someone is always formally responsible for their welfare — tracked in real time, not reconstructed after an incident from email threads and PDF contracts. It means that when things go wrong, the system handles it. Not because someone made a phone call, but because the protocol already knows what to do.
For the industry, it means the network effect finally works in everyone's favour. A small activity provider in a regional destination publishes one structured profile and becomes discoverable by every platform that implements the protocol. A major OTA builds one integration and accesses every supplier in the network. The bilateral integration burden — the N×M matrix of custom connections that currently makes activity booking so expensive to scale — collapses.
For regulators, it means that the accountability chain for AI-mediated travel is no longer invisible. Every AI agent holds a declared, verified authority scope. Every duty of care transfer is timestamped. The compliance record exists before it is needed, not after.
The travel industry has always been good at relationships. Hotels know their suppliers. Tour operators know their guides. OTAs know their hotel partners. What has been missing is the shared infrastructure that makes those relationships machine-readable, scalable, and resilient when something goes wrong.
The Activity Travel Protocol is that infrastructure. It does not change the relationships. It gives them a common language.
The specification is live at activitytravel.pro. The conversation about what gets built on it starts now.