The Corporate Travel Problem
Corporate travel is one of the first domains where autonomous agents are replacing human workflows at scale. AI assistants book flights, reserve hotel rooms, arrange car rentals — all without a human clicking "confirm." Concur, Navan, and a new wave of agent-first platforms are building exactly this.
But the trust layer is completely missing. When an AI agent books a $900 hotel room on behalf of an employee, the hotel has no way to verify:
- Did the company actually authorize this agent to book?
- Is the employee the real principal, or was the agent compromised?
- Is hotel booking within this agent's allowed segments?
- What's the spend limit — and is this booking within it?
- Who's accountable when the booking goes wrong?
The Missing Link: Delegation Chains
Shopping is simple — one person, one agent, one purchase. Travel is different. Corporate travel involves a chain of delegated authority:
Company → authorizes HR to set travel policies
HR / Manager → authorizes employee travel budgets
Employee → delegates to AI travel agent
AI Travel Agent → books with airlines, hotels, rental companies
Each link in this chain is a trust boundary. If any link is broken — a compromised agent, an exceeded budget, an unauthorized segment — the entire booking should be flagged. No travel platform today verifies this chain cryptographically.
That's what MT Travel solves. We built the TravelAgentCredential — a W3C Verifiable Credential that encodes the full delegation chain, segment permissions, spend limits, and traveler identity into a single, cryptographically verifiable credential.
Introducing TravelAgentCredential
A TravelAgentCredential binds an AI booking agent to its principal through a verifiable delegation chain. It's not just "this agent can book" — it's "this agent can book hotels up to $500/night for this employee, authorized by this company, until this date."
Delegation Chain
Cryptographic chain from company → manager → employee → agent. Every link verified.
Segment Permissions
Hotel, flight, car rental, rail — each segment independently authorized. No scope creep.
Spend Limits
Per-booking and daily caps. A $200/night hotel credential can't book a $1,200 suite.
Traveler Identity
Credential binds to a specific traveler. Agent can't book for unauthorized passengers.
How the Protocol Works
Step 1: Issue a TravelAgentCredential
Step 2: Agent Books Travel
The agent searches for flights, selects hotels, and initiates checkout — presenting its TravelAgentCredential as proof of authorization. The credential travels with every booking request.
Step 3: Merchant Verifies
Before confirming the reservation, the merchant calls MoltGuard's verification endpoint. One POST. Ten checks. Sub-second response.
The 10-Step Verification Pipeline
Every booking passes through a 10-step verification pipeline. Each check must pass independently. A single failure produces a rejected result with a specific reason.
| # | Check | What It Verifies |
|---|---|---|
| 1 | VC Signature | Ed25519 JWS is valid and not tampered |
| 2 | VC Expiry | Credential hasn't expired |
| 3 | Agent DID Match | Requesting agent matches credential subject |
| 4 | Segment Authorization | Hotel/flight/car is in allowed segments |
| 5 | Spend Limit | Booking amount ≤ credential spend limit |
| 6 | Currency Match | Payment currency matches credential currency |
| 7 | Daily TX Cap | Agent hasn't exceeded daily booking limit |
| 8 | Trust Score | On-chain agent reputation ≥ threshold |
| 9 | Delegation Chain | Authority chain is complete and valid |
| 10 | Traveler Binding | Booking is for the authorized traveler |
Multi-Segment Trips — One Trip, One Receipt
A business trip is rarely a single booking. It's a flight + hotel + car rental. MT Travel groups these into a single trip with a shared tripId.
This gives finance teams a single audit trail for a complete trip, with every segment independently verified and anchored on-chain.
MT Shopping vs. MT Travel
MT Travel builds on the same credential architecture as MT Shopping, but adds the complexity that travel demands.
| Dimension | MT Shopping | MT Travel |
|---|---|---|
| Credential | BuyerAgentCredential | TravelAgentCredential |
| Delegation | Human → Agent | Company → Manager → Employee → Agent |
| Segments | Product categories | Hotel, flight, car rental, rail |
| Trip Grouping | N/A | Multi-segment tripId linking |
| Traveler Binding | N/A | Named traveler on credential |
| Verification Steps | 7 | 10 |
| On-Chain Receipts | Per purchase | Per segment + per trip |
Why This Matters Now
Corporate travel management platforms are racing to add AI agents. Concur, Navan, TripActions — all are building or acquiring agent capabilities. But they're doing it inside their own silos, with proprietary authorization that doesn't translate across platforms.
When an employee's AI agent books a Hilton room through Navan, then a Lufthansa flight through Concur, there's no unified credential that spans both platforms. No single audit trail. No portable authorization.
The travel industry doesn't need more proprietary agent APIs. It needs an open credential standard that works across every platform, airline, and hotel chain.
MT Travel is that standard. W3C Verifiable Credentials. Ed25519 signatures. On-chain anchoring on Base. Open endpoints. No SDK lock-in.
Get Started
All MT Travel endpoints are free during Early Access. No signup, no API key, no SDK — just HTTP.
- View the TravelAgentCredential schema
- Read the API reference
- Visit the MT Travel landing page
- Compare with MT Shopping
Issue Your First TravelAgentCredential
All endpoints free during Early Access. Start verifying agent bookings today.
Get Started →MT Travel is built by MolTrust (CryptoKRI GmbH, Zurich) — trust infrastructure for the agent economy. Follow @MolTrust on X for updates.