Agent
The airline, OTA or provider selling a flight offer. The same itinerary can be sold by multiple agents with different prices and conditions.
Why it matters
In the flight domain, itinerary, leg, segment, carrier and seller identity are distinct. Flattening them too aggressively mixes schedule, fare, agent and booking rules. The search UI can be simple, but the source model needs enough detail for repricing and handoff.
What does it look like in practice?
The same itinerary can be sold by multiple agents with different fare brands, baggage and booking conditions. Segment schedule and seller/offer identity are different concepts.
Implementation questions
- Which legs and segments form the itinerary?
- Are marketing and operating carriers separated?
- Is agent/provider identity retained?
- Is the source reference available for repricing?
Common mistakes
- Modeling an offer as flight number plus price
- Mixing marketing and operating carriers
- Embedding agent identity into itinerary identity
Where does it appear in the travel stack?
Agent commonly appears across flight, agentic layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Agentic Travel Reference Architecture
Design AI agent → search → offer → reprice → confirmation → payment → booking → servicing with travel-specific authorization, idempotency and audit boundaries.
Explore →Agentic Travel Servicing, Consent and Auditability
Design agent-driven cancellation, refund and servicing with explicit consent, traceability, versioned evidence and post-booking authorization boundaries.
Explore →Agentic Travel Transaction Safety
Prevent duplicate booking and payment caused by agent loops, retries and tool invocation using idempotency, side-effect guards and UNKNOWN-aware recovery.
Explore →Travel Payment Ownership: Merchant of Record, Seller of Record and Collect Models
Separate Merchant of Record, Seller of Record, agency collect, hotel collect and pay-at-property models across booking and reconciliation.
Explore →Google Flights in Turkey: Flight Discovery and Booking Handoff
Understand Google Flights in Turkey across discovery, airline/OTA seller options, TRY display and booking handoff.
Explore →Google Flights: Partner Access, Offers and Booking Handoff
Understand Google Flights partner access, itinerary and seller ranking, fare equivalence and booking handoff through practical operational scenarios.
Explore →