Get scheduled departures for any airport via FlightAware AeroAPI, pay-per-request at $0.01.
What it does
This endpoint returns scheduled departure flights for a specific airport, sourced from FlightAware's AeroAPI. It is part of the StableTravel platform, which wraps Amadeus, FlightAware, and Google Flights data behind pay-per-request micropayment endpoints. The endpoint accepts an airport identifier (ICAO or IATA code) as a path parameter and supports optional query parameters for airline filtering, pagination via cursor, and max_pages control. It returns an array of scheduled_departures, each containing flight ident, operator, origin/destination airport details, scheduled/estimated/actual times, aircraft type, route distance, gate and terminal info, and status fields.
Pricing is $0.01 per request, settled via MPP (Tempo method on chain 4217) or x402 protocol using USDC. No API keys or subscriptions are required — payment serves as authentication. The response schema includes pagination links and num_pages for iterating through large result sets. This endpoint is useful for building departure boards, monitoring airport operations, or feeding scheduled flight data into travel planning agents.
The endpoint is live, confirmed by a 402 MPP challenge response. The full OpenAPI 3.1 spec is published at stabletravel.dev/openapi.json with detailed response schemas for the scheduled_departures array.
Capabilities
Use cases
- —Building a real-time departure board for an airport
- —Monitoring scheduled departures for a specific airline at an airport
- —Feeding scheduled departure data into a travel planning agent
- —Alerting on upcoming departures from a given airport
- —Aggregating departure schedules across multiple airports
Fit
Best for
- —AI agents that need airport departure schedules without API key management
- —Applications building departure boards or airport operations dashboards
- —Travel planning workflows that need upcoming flight schedules
Not for
- —Booking flights (use the Amadeus flight booking endpoints instead)
- —Historical departure data (use the FlightAware history endpoints instead)
- —Real-time in-flight position tracking (use the flight track/position endpoints instead)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/flights/scheduled-departures"Example
Response
{
"links": {
"next": null
},
"num_pages": 1,
"scheduled_departures": [
{
"ident": "UAL123",
"origin": {
"city": "New York",
"code": "KJFK",
"name": "John F Kennedy Intl",
"code_iata": "JFK"
},
"status": "Scheduled",
"operator": "UAL",
"ident_iata": "UA123",
"destination": {
"city": "Los Angeles",
"code": "KLAX",
"name": "Los Angeles Intl",
"code_iata": "LAX"
},
"gate_origin": "B22",
"fa_flight_id": "UAL123-1718000000-schedule-0000",
"scheduled_in": "2025-06-15T19:45:00Z",
"scheduled_on": "2025-06-15T19:30:00Z",
"aircraft_type": "B738",
"operator_iata": "UA",
"scheduled_off": "2025-06-15T14:15:00Z",
"scheduled_out": "2025-06-15T14:00:00Z",
"terminal_origin": "7"
}
]
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, live 402 MPP challenge confirmed, clear pricing ($0.01/request), comprehensive documentation including parameter descriptions and pagination. Only minor gap is lack of a real example response in the docs.
Citations
- —Endpoint price is $0.01 per requesthttps://stabletravel.dev/openapi.json
- —Endpoint is live, confirmed by 402 MPP challenge with method tempo on chain 4217https://stabletravel.dev/api/flightaware/airports/:id/flights/scheduled-departures
- —Payment via USDC on Base, Solana, or Tempo; no API keys neededhttps://stabletravel.dev
- —Data sourced from FlightAware AeroAPIhttps://stabletravel.dev/docs
- —Accepts ICAO or IATA airport code as path parameter, optional airline and pagination query paramshttps://stabletravel.dev/openapi.json