Historical flights between two airports via FlightAware AeroAPI, pay-per-request at $0.24/call.
What it does
This endpoint returns historical flight data between a specified origin airport and destination airport. It is part of StableTravel's FlightAware history suite, which proxies FlightAware AeroAPI through a pay-per-request micropayment model. The URL pattern is `/api/flightaware/history/airports/:id/flights/to/:dest_id`, where `:id` is the origin airport code (ICAO or IATA, e.g. KJFK or JFK) and `:dest_id` is the destination airport code. The endpoint accepts GET requests and supports optional query parameters: `start` and `end` (ISO 8601 date strings to bound the time range), `max_pages` (number of pages to fetch), and `cursor` (opaque pagination token). The response contains a `flights` array with detailed flight objects including fa_flight_id, ident, operator, origin/destination info, scheduled/actual times, delays, aircraft type, route distance, and more.
Pricing is $0.24 per request, settled via MPP (Tempo method on chain 4217) or x402 protocol using USDC-equivalent stablecoin. No API keys or subscriptions are required — payment serves as authentication. The endpoint was confirmed live via a 402 MPP challenge with amount 240000 base units (6 decimals = $0.24). The full OpenAPI 3.1 schema is published at stabletravel.dev/openapi.json with complete parameter and response definitions.
Capabilities
Use cases
- —Analyzing historical flight frequency and patterns between two airports
- —Researching on-time performance for a specific airport pair over a date range
- —Building datasets of past flights for route planning or analytics
- —Checking which airlines historically operated a given city pair
- —Auditing historical delays and cancellations on a route
Fit
Best for
- —Agents needing historical aviation data without FlightAware API key management
- —One-off or low-volume historical flight lookups where subscription pricing is wasteful
- —Autonomous travel-planning agents that need route history context
Not for
- —Real-time flight tracking (use the live FlightAware endpoints instead)
- —Bulk historical data export requiring thousands of pages (cost adds up at $0.24/call)
- —Booking flights (use the Amadeus flight search/book endpoints)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/airports/JFK/flights/to/LAX"Example
Response
{
"links": {
"next": null
},
"flights": [
{
"ident": "AAL1",
"origin": {
"city": "New York",
"code": "KJFK",
"name": "John F Kennedy Intl",
"code_iata": "JFK"
},
"status": "Arrived",
"operator": "AAL",
"actual_in": "2025-01-10T11:45:00Z",
"actual_out": "2025-01-10T08:12:00Z",
"ident_iata": "AA1",
"destination": {
"city": "Los Angeles",
"code": "KLAX",
"name": "Los Angeles Intl",
"code_iata": "LAX"
},
"fa_flight_id": "AAL1-1718000000-schedule-0001",
"aircraft_type": "B772",
"arrival_delay": 300,
"operator_iata": "AA",
"scheduled_out": "2025-01-10T08:00:00Z",
"route_distance": 2475,
"departure_delay": 720
}
],
"num_pages": 1
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed parameter and response definitions, live 402 MPP challenge confirmed, clear pricing ($0.24), comprehensive documentation. Minor deduction: no worked example response in the docs, and the specific endpoint path uses parameterized segments that aren't individually documented beyond the OpenAPI spec.
Citations
- —Endpoint price is $0.24 per request for historical flights between airportshttps://stabletravel.dev/openapi.json
- —MPP challenge confirmed live with amount 240000 base units on Tempo chain 4217https://stabletravel.dev/api/flightaware/history/airports/:id/flights/to/:dest_id
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Supports query parameters start, end, max_pages, cursor for filtering and paginationhttps://stabletravel.dev/openapi.json
- —Response contains flights array with fa_flight_id, ident, origin, destination, delays, status, and pagination linkshttps://stabletravel.dev/openapi.json