Under development
Tripicon Context Pass
Travel systems know parts of the traveller. AI agents rarely receive the context they need.
Concept and interoperability model under development. No production traveller-context service is currently offered, and Context Pass is not an identity document or a central repository of complete traveller records.
- Corporate travel
- Events and conferences
The idea
Preferences set once. Context resolved when needed.
Travellers repeatedly enter the same preferences across booking systems, event registrations, hotels and digital assistants. Meanwhile, organisations already hold policy, itinerary, accessibility, dietary and service information that remains isolated inside separate systems.
Interests, pace, accessibility requirements, dietary preferences, transport preferences and travelling-party needs.
Stable. Controlled by the traveller.Dates, available time, weather, location, confirmed bookings and event commitments.
Resolved for a specific request. Not retained as a permanent profile.Who it is for
Built for organisations, not as another consumer travel app.
The initial focus is corporate travel and events, where organisations already have established relationships with travellers and already manage profiles, permissions, policies or registrations.
Context Pass is intended to connect with existing systems. It is not intended to replace corporate travel platforms, event-registration systems, hotel PMS platforms or customer CRMs. Source systems remain the systems of record.
The other half
Matching needs better information from travel organisations.
Traveller context alone is not enough. For an authorised agent to assemble a suitable journey, hotels, destinations, venues, attractions and operators have to publish far more precise machine-readable detail than they do today.
- Weather contingencyCovered or exposed, operation in rain, heat or wind, shelter while waiting, alternatives offered.
- Time-of-day suitabilityEarliest realistic start, latest useful arrival, minimum worthwhile duration, transport after finishing.
- Accessibility detailStep-free route, surface and gradient, seating frequency, sensory environment, and when it was last verified.
- SeasonalityOperating season, seasonal closures, daylight dependency, seasonal transport and staffing limits.
- Realistic duration and transfersTypical duration range and transfer time by transport mode, not an optimistic estimate.
- Cluster compatibilityWhat works before and after, energy level, meal timing, luggage and companion suitability, fallbacks.
Tripicon is developing a model that connects traveller context with verified organisational attributes and workable experience clusters.
How it fits
Separate from Tripicon’s existing offers.
Each offer is designed to provide value independently. A Representation Review is not required to use a future Context Pass or Tripicon Platform service.
Measures how major AI systems publicly describe a travel organisation, identifies their sources and highlights representation risks. Uses public information only.
Enables travel organisations to design, manage and activate the knowledge, relationships, experiences and experience sequences that AI systems use.
Provides a controlled mechanism for authorised systems to use relevant traveller context.
You are here
Current status
A product concept under development.
The data model, interoperability approach, governance controls and initial enterprise use cases are being validated. Context Pass is not currently offered as a production traveller profile, identity wallet or live data-exchange service.
Better AI travel experiences require two things: trustworthy information about what organisations can deliver, and permission to understand what the traveller actually needs.
Discuss an enterprise use case
We are looking for design partners in corporate travel and events — organisations that already hold traveller profiles and want to make them usable by authorised agents.