Activity Travel Protocol is an open standard for the global travel industry, governed by an independent foundation in formation. It enables the discovery, booking, fulfillment, and duty-of-care management of complex, multi-supplier travel experiences — with AI agent participation built into the protocol from the ground up.
The full protocol specification — four layers covering identity, discovery, workflow, and schema. Layers 1–3 published.
Read the specification → NewAnalysis, industry context, and technical commentary from the founding maintainer — for industry professionals and policy makers.
Read the blog → FoundationThe Activity Travel Protocol Foundation (in formation / 設立準備中) is being established as the independent standards body that will govern the protocol. No single commercial entity owns or controls the standard.
Foundation & Charter →From the Founder
Wouldn't it be nice if you could book sightseeing and activities alongside your hotel and transport —and then have someone looking out for you throughout your entire journey, until you arrive home safely?
A vacation isn't just a hotel room. People want the full experience: the guided tour, the activity, the restaurant, the transfer —assembled together and working as one.
But today's OTA and hotel booking systems weren't built for this. They handle discrete inventory: a seat, a room, a car. Complex, multi-supplier activity experiences —where a dozen providers need to collaborate to build a single itinerary —fall outside what any existing protocol can handle. Without a common language for suppliers to communicate, they simply cannot work together.
The natural conclusion is to build that protocol. Easier said than done.
Supporting a traveller from the moment they begin booking until they arrive home safely —across multiple suppliers, jurisdictions, and AI agents —is an order of magnitude more complex than anything the travel industry has standardised before. The Activity Travel Protocol is designed as a runtime platform: a Travel Operating System that manages the full lifecycle of a booking, with trust, policy enforcement, duty of care, and AI agent participation built into the protocol itself.
The value to the industry and to travellers is clear. But building an open protocol of this scope and releasing it under an Apache 2.0 licence is not something a commercially competitive company would do for its own account. That is precisely why an independent founder needs to build it.
So I decided to build it —with the help of Claude. Not just the protocol specification, but the full SDK.
This protocol is still a work in progress. When it is ready, I will make a formal announcement.
Thank you.
The Activity Travel Protocol is organized into four layers — from identity and trust through to schema and SDK — each building on the last. Layers 1–3 are complete and published. Layer 4 is in active development.
Party registry, verifiable credentials, jurisdiction compliance, and agentic authorization. Establishes who the parties are and what they are permitted to do.
Supplier capability declarations, activity configurations, resource definitions, and pricing structures. Describes what suppliers offer before any booking begins.
The state machine governing the full booking lifecycle — from inquiry through negotiation, confirmation, fulfillment, disruption management, and completion.
Precise data structures for every protocol object and message, with a full SDK including atp-core, atp-agent, atp-mcp, and nine additional packages.
Work in Progress
This protocol is a work in progress. There are substantial parts that have yet to be published. No third party review, yet. We welcome inputs and suggestions — please contact us.
Get in Touch
Consortium membership, press, developer interest, and general enquiries are all welcome.
AI agents and automated systems are welcome to use this form. An email address is not required — include an X handle, Discord handle, GitHub username, or other contact method in the handle field below.