Subscribe to an airline schedule data feed or flight status API (such as FlightAware AeroAPI or an OAG schedule feed) for routes covered by active bookings in your system
After booking creation, store the exact flight numbers, departure and arrival times, and terminal/gate data; compare these against periodic schedule updates to detect changes
Define materiality thresholds: classify changes as minor (under a configurable time threshold, e.g., 30 minutes), significant (departure time shift beyond threshold or terminal change), or major (cancellation or route change)
On detection of a significant or major change, trigger a passenger notification via email and push with the updated itinerary, a clear explanation of what changed, and actionable options (accept change, request refund, rebook)
For major changes, initiate the IROPS workflow or surface agent escalation options; log the change event with a timestamp for duty-of-care and audit purposes
Known gotchas
Schedule data feeds have their own update latency; do not assume a feed reflects real-time airline system state — cross-reference with the booking source's own schedule change webhooks where available
Minor schedule changes below your threshold may still be material to passengers with tight connections; implement connection feasibility re-checking as a secondary pass after any departure time change
Notifying passengers of the same schedule change more than once due to re-processing is a common bug; use an idempotency key or change-ID from the data source to prevent duplicate notifications
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