Repeated traveller data
Identity, preferences, loyalty and payment details are re-entered across disconnected systems.
A governed MCP / AI / API foundation
One travel platform.
Every journey.
From intent to booking, safety, servicing and finance—connected through one accountable travel core.
OAuth 2.0/api/v1/mcp
The client reality
Travel is fragmented.
The experience should not be.
Manual operations
Bookings, changes, payments, documents and accounting are reconciled by hand.
Integration duplication
Every new application rebuilds supplier connections, controls, policy and audit.
One governed path
The platform model
One governed gateway.
Many experiences.
CLIENT EXPERIENCES
OBT / CBTTravellerConsultantOperationsPartners
OAuth 2.0/api/v1/mcpWebhooks
TRAVEL COREProfiles · Policy · Approval · Workflows · AI · Tools · Audit · Evidence
REPLACEABLE RAILS
Travel contentPCI vaultCommunicationsRisk intelligenceDocuments & finance
A continuous operating lifecycle
From travel intent to
operational closure.
- 01UnderstandText · voice · image · OCR
- 02PlanAir · hotel · vehicle · policy
- 03ApproveAuthority · consent · mandate
- 04Book & payPNR · ticket · secure payment
- 05Travel safelyRisk · welfare · escalation
- 06ServiceChange · cancel · refund
- 07CloseDocuments · finance · reconcile
The capability landscape
A complete travel
operating capability.
Travel
Coregoverned once
Coregoverned once
Journey
Shop · price · book · ticket · service
Profile
Traveller · company · preferences · consent
Safety
Risk · welfare · emergency escalation
Intelligence
Voice · image · OCR · agents
Operations
Documents · accounting · reconciliation
Ecosystem
OAuth · REST · MCP · SDK · webhooks
Profile manager
Tell us once.
Reuse responsibly.
- Identity, loyalty, preferences and policy context
- Consented emergency contacts and next-of-kin rules
- Masked payment metadata—never PAN or CVV
- Revision history, provenance and per-trip snapshots
- Authorised reuse without cross-tenant leakage
Secure booking and payment
Booking power without
payment-data exposure.
Core stores: opaque token + masked metadata Core never stores: card number or security code
Duty of care
Safety that follows
the journey.
- 01Authorised itinerary activates monitoring
- 02Risk feeds match affected travellers
- 03Multi-channel welfare check
- 04SAFE or ASSISTANCE REQUIRED
- 05Approval-bound escalation and human response
Multimodal intelligence
AI assists.
Core remains in control.
AIgoverned
AI proposes and interprets. Identity, policy, permissions and evidence remain authoritative.
The journey does not end at ticketing
Every journey closes
operationally and financially.
Documents
Itineraries, receipts, vouchers and service confirmations
Accounting
Canonical invoices, credits and system handoffs
Communications
Traveller, consultant, approver, operations and accounts
Reconciliation
Resolve uncertain outcomes without blind retries
Enterprise control
Trust is designed into
every action.
AUTHORITYTenant · application · user · roles · permissions
CONTROLPolicy · approval · mandate · idempotency
EVIDENCETrace · audit · usage · provenance · reconciliation
Provider-neutral public responsesSecret and destination redactionBounded agents and retriesNo unrestricted SQL, shell or filesystem tools
Honest readiness
Proven platform.
Explicit activation boundary.
163/163
Full regression tests passed
Implemented & regression-tested
OAuth · /api/v1 · MCP · profiles · travel workflows · duty of care · payment boundary · AI/media · documents · accounting · audit
External activation required
PCI-vault account and Pay route certification · carrier credentials and delivery certification · contracted risk intelligence and human assistance
One foundation. Many opportunities.
Build the client experience once.
Connect to the travel core.
Corporate OBT / CBTConsultant copilotOperations controlTraveller safetyWhite-label applicationsPartner marketplaceFinance automationIndustry-specific agents
START HEREConnect the first external travel application
OAuth 2.0 · /api/v1 · /mcp