An open protocol standard for the global travel industry.
The Activity Travel Protocol enables the discovery, configuration, negotiation, booking, fulfillment, and disruption management of complex travel activities and experience packages across multiple suppliers, jurisdictions, and AI agents.
The Activity Travel Protocol is not a message format specification. It is a runtime platform — a Travel Operating System — that manages the full lifecycle of a booking as a first-class runtime entity, with policy enforcement, trust chain construction, duty of care tracking, and AI agent participation built into the protocol itself.
activitytravel.pro — full specification, working drafts, and standards positions.
Layer 1 — Identity and Trust: Complete. Nine specifications published.
Layers 2, 3, and 4 are in design. The SDK has not yet started.
| Layer | Name | Status |
|---|---|---|
| Layer 1 | Identity and Trust | Complete — 9 specifications published |
| Layer 2 | Discovery and Capability | Not yet started |
| Layer 3 | Workflow | Not yet started |
| Layer 4 | Schema and SDK | Placeholder |
| Document | File |
|---|---|
| Architecture Specification | docs/spec/architecture.md |
| Protocol Charter | docs/spec/CHARTER.md |
| Party Registry Specification | docs/spec/party-registry.md |
| Jurisdiction Compliance Specification | docs/spec/jurisdiction-compliance-spec.md |
| Jurisdiction Entries | docs/spec/jurisdiction-entries.md |
| Global Jurisdiction Comparison | docs/spec/jurisdiction-discussion-paper.md |
| Trust Chain Declaration Specification | docs/spec/trust-chain.md |
| Party Policy Declarations Specification | docs/spec/party-policy-declarations.md |
| References | docs/spec/references.md |
The Activity Travel Protocol is governed independently. MyAuberge (Hakuba/Chino, Nagano, Japan) is the founding maintainer with no special commercial rights.
The protocol is open and free under Apache 2.0.
Consortium membership: open an Issue titled Consortium Membership — [Organisation Name].
Specification contributions: open a Pull Request with a clear description of the change and the rationale.
Apache 2.0. See LICENSE.