After retrieving a flight offer from the Amadeus Flight Offers Search API, locate the pricingOptions and travelerPricings arrays within each offer object.
Within each travelerPricing, inspect the fareDetailsBySegment array; each entry contains a includedCheckedBags object with quantity (number of bags) or weight (in kg or lb) and weightUnit fields.
If the includedCheckedBags quantity is 0, the fare is typically carry-on only; surface this prominently as baggage fees may apply at check-in.
For cabin baggage, check for a includedCabinBags object if present; note that carry-on dimensions and weight limits vary by carrier and are not always in the API response.
When displaying allowances, group by segment because long-haul and short-haul legs within the same booking may have different baggage rules.
To get the most accurate baggage data, re-confirm allowances via the flight offers pricing endpoint before order creation, as allowances can differ from initial search results.
Known gotchas
Baggage data in search results may be absent or incomplete for some carriers; always re-price via the pricing endpoint for authoritative allowance details.
Weight-based and piece-based allowances coexist in the same itinerary for interline routes — display both dimensions when present rather than picking just one.
Allowances for paid baggage ancillaries are separate from included allowances and must be fetched from the ancillary services endpoint — do not confuse the two.
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