Get current delay information for a specific airport via FlightAware AeroAPI, pay-per-request at $0.02.
What it does
This endpoint returns current delay information for a specific airport, identified by its ICAO or IATA code (e.g., KJFK or JFK). It is part of the StableTravel platform, which wraps FlightAware's AeroAPI behind a pay-per-request micropayment layer. The response includes an array of delay objects, each containing the airport name, airport code, a color-coded severity indicator, and an array of delay reasons with category, color, delay duration in seconds, and affected flight count.
The endpoint costs $0.02 per request, paid via MPP (Tempo method on chain 4217) or x402 protocol using USDC. No API keys, OAuth tokens, or subscriptions are required — payment serves as authentication. The endpoint accepts GET requests with the airport identifier as a path parameter (replacing `:id` in the URL). Data is sourced from FlightAware's AeroAPI, providing real-time operational delay data including weather delays, ground stops, and other disruption categories.
This endpoint is part of a larger StableTravel API suite covering flights (Amadeus GDS), hotels, activities, transfers, Google Flights price comparison, and extensive FlightAware operational data including flight tracking, airport weather (METAR/TAF), disruption counts, and flight history.
Capabilities
Use cases
- —Check current delays at a specific airport before traveling
- —Monitor airport operational status for travel agent bots
- —Build disruption dashboards showing per-airport delay severity
- —Integrate airport delay data into itinerary planning workflows
- —Alert travelers about delays at their departure or arrival airport
Fit
Best for
- —AI travel agents that need real-time airport operational status
- —Autonomous trip planners checking for disruptions before booking
- —Aviation operations dashboards needing per-airport delay feeds
Not for
- —Historical delay analytics (use the history endpoints instead)
- —Flight-level delay tracking for a specific flight number (use /flights/{ident} instead)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/delays"Example
Response
{
"delays": [
{
"color": "yellow",
"airport": "John F Kennedy Intl",
"reasons": [
{
"color": "yellow",
"count": 42,
"category": "weather",
"delay_secs": 1800
}
],
"airport_code": "KJFK"
}
]
}Endpoint
Quality
Full OpenAPI 3.1 schema with response structure, clear pricing ($0.02/request), live MPP 402 challenge captured, comprehensive documentation including parameter details and workflow guidance. Only minor gap: no example response in the spec itself (the example above is inferred from the schema).
Citations
- —Endpoint price is $0.02 per requesthttps://stabletravel.dev/openapi.json
- —Payment via MPP Tempo method on chain 4217 or x402https://stabletravel.dev/openapi.json
- —Response contains delays array with airport, airport_code, color, and reasons fieldshttps://stabletravel.dev/openapi.json
- —Airport identifier accepts ICAO or IATA codes (e.g. KJFK, JFK)https://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC serves as authenticationhttps://stabletravel.dev
- —Data sourced from FlightAware AeroAPIhttps://stabletravel.dev/docs