Get real-time departure flights from any airport via FlightAware AeroAPI for $0.01 per request.
What it does
This endpoint returns departure flight data for a specific airport, powered by FlightAware AeroAPI and proxied through StableTravel. You provide an ICAO or IATA airport code as a path parameter (e.g., KJFK or JFK) and receive a paginated list of departure flights including ident, operator, origin/destination details, scheduled/estimated/actual times, delays, aircraft type, gate, terminal, baggage claim, and flight status. Optional query parameters let you filter by airline IATA code, control pagination with max_pages and cursor.
The endpoint costs $0.01 per request, paid 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 includes a `departures` array of flight objects with comprehensive operational data, plus `links.next` for cursor-based pagination and `num_pages` count.
This is part of the broader StableTravel API suite which covers flights (Amadeus GDS), hotels, activities, transfers, Google Flights price comparison, and the full FlightAware AeroAPI surface including real-time tracking, airport info, weather, flight history, and disruption counts. All endpoints follow the same pay-per-request model with no signup required.
Capabilities
Use cases
- —Building a live airport departure board for a travel app or kiosk
- —Agent autonomously checking if a specific flight has departed on time
- —Monitoring all departures from an airport filtered by a specific airline
- —Feeding departure data into a travel planning agent for connection timing
- —Operational dashboards tracking airport throughput and delays
Fit
Best for
- —AI agents that need real-time airport departure data without managing API keys
- —Travel applications requiring live departure boards
- —Autonomous trip-planning agents checking flight operations
- —Developers who want pay-per-call FlightAware data without a subscription
Not for
- —Historical departure analysis (use /api/flightaware/history/airports/{id}/flights/departures instead)
- —Flight price comparison or booking (use Amadeus or Google Flights endpoints)
- —Bulk data export of all global departures
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/flights/departures"Example
Response
{
"links": {
"next": null
},
"num_pages": 1,
"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-0001",
"registration": "N12345",
"aircraft_type": "B738",
"estimated_out": "2025-06-15T14:10:00Z",
"flight_number": "123",
"operator_iata": "UA",
"scheduled_out": "2025-06-15T14:00:00Z",
"departure_delay": 600,
"terminal_origin": "7"
}
]
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, clear pricing ($0.01/request), live MPP 402 challenge confirmed, comprehensive documentation with parameter descriptions and query options. Only minor gap is lack of a concrete example response in the spec itself.
Citations
- —Endpoint price is $0.01 per requesthttps://stabletravel.dev/openapi.json
- —Payment via MPP Tempo method (chainId 4217) or x402, no API keys requiredhttps://stabletravel.dev/openapi.json
- —Endpoint is live, confirmed by 402 MPP challenge on HEAD requesthttps://stabletravel.dev/api/flightaware/airports/:id/flights/departures
- —Data sourced from FlightAware AeroAPIhttps://stabletravel.dev
- —Optional query parameters include airline, type, max_pages, cursorhttps://stabletravel.dev/openapi.json