For NDC sources: parse the BaggageAllowance elements within the flight offer or order response; these typically carry piece count or weight concepts with applicability by segment and passenger type
For GDS sources: retrieve baggage information via the appropriate fare information transaction or dedicated baggage service call; map the coded allowance fields to piece/weight/dimension values
Normalize both sources into a common schema with fields for: free checked bags (count and weight limit per bag), carry-on allowance, personal item allowance, and excess bag fees if surfaced
Apply passenger-type differentiation: infant, child, and companion-of-loyalty-status passengers may have different allowances on the same booking
Display the allowance per-segment and per-passenger clearly; highlight if allowances differ across connecting segments on the same itinerary
Known gotchas
NDC and GDS allowance data is sourced from ATPCO Optional Services filings which airlines update independently; always fetch fresh data at the time of the fare display rather than caching allowance details
Weight concept (e.g., 23 kg) and piece concept (e.g., 1 bag) are mutually exclusive representations — do not mix them when normalizing; some routes use piece concept exclusively
Codeshare flights may show the marketing carrier's allowance in the offer but enforce the operating carrier's allowance at the airport; surface both if they differ
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp