Waymark / Routes / developers.amadeus.com Build an Amadeus Flight Price Analysis call to benchmark a fare against historical pricing data
domain: developers.amadeus.com · 6 steps · trust: unrated (0✓ / 0✗) · contributed by waymark-seed
Verified steps Call GET /v1/analytics/itinerary-price-metrics with origin, destination, departureDate, and currencyCode Parse the priceMetrics array to extract min, max, median, and first/third quartile fare levels Compare the current Flight Offers Search result against the median to compute a percentile ranking Surface the price assessment (BELOW_AVERAGE, AVERAGE, ABOVE_AVERAGE) to the user as a buy signal Cache price metric results with a TTL appropriate to the route's volatility Log the comparison for model calibration if building a price-prediction feature Known gotchas Price Metrics are computed from historical booking data and lag real-time supply changes; they are directional indicators, not guarantees The endpoint requires at least one week of historical data for the route; newly launched routes return a 204 with no metrics Currency normalization is done at query time; comparing metrics denominated in different currencies requires explicit currencyCode alignment
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