Get historical flight route info (fixes, waypoints, distance) via FlightAware AeroAPI for $0.08/request.
What it does
This endpoint returns the filed route for a historical flight, including the sequence of navigation fixes/waypoints with their names, types, and geographic coordinates, plus the total route distance. It is part of the StableTravel platform, which wraps FlightAware's AeroAPI behind a pay-per-request MPP/x402 micropayment layer. The endpoint accepts a FlightAware flight ID as a path parameter and returns structured JSON.
The endpoint costs $0.08 per request, settled via USDC on Tempo (chainId 4217) or x402. No API keys, OAuth tokens, or subscriptions are required — payment serves as authentication. The endpoint is live, returning a 402 MPP payment challenge when probed without payment, confirming it is operational.
This is one of several FlightAware history endpoints on StableTravel. Related endpoints include historical flight track (position history at $0.12), historical flight map image ($0.28), and historical flights by ident ($0.04). The typical workflow is: look up historical flights by ident to get a fa_flight_id, then call this route-info endpoint with that ID. The response schema includes a `fixes` array (each with name, type, latitude, longitude) and an optional `route_distance` number.
Capabilities
Use cases
- —Retrieve the filed route and waypoints for a completed flight for post-flight analysis
- —Build historical route visualizations by combining fixes with lat/lng coordinates
- —Compare filed routes across multiple historical flights on the same city pair
- —Audit operator routing patterns over time using historical route data
- —Feed historical route fixes into aviation analytics or compliance tools
Fit
Best for
- —Aviation data analysts needing historical filed routes and waypoints
- —Agents building post-flight reports or route comparison tools
- —Developers who want FlightAware AeroAPI data without managing API keys or subscriptions
Not for
- —Real-time in-flight route tracking (use the live route-info or track endpoints instead)
- —Booking flights or hotels (use the Amadeus-backed StableTravel endpoints)
- —Free or bulk historical data downloads (this is pay-per-request at $0.08 each)
Quick start
# Get historical route info for a flight by fa_flight_id
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/flights/UAL100-1234567890-airline-0123/route-info"Example
Response
{
"fixes": [
{
"name": "KJFK",
"type": "Origin",
"latitude": 40.6399,
"longitude": -73.7787
},
{
"name": "MERIT",
"type": "Named Fix",
"latitude": 40.85,
"longitude": -73.45
},
{
"name": "KLAX",
"type": "Destination",
"latitude": 33.9425,
"longitude": -118.4081
}
],
"route_distance": 2475
}Endpoint
Quality
Full OpenAPI 3.1 schema with response structure, clear pricing ($0.08 USD per call), live 402 MPP challenge captured, comprehensive guidance docs. Slightly below 0.9 because no real example response data was captured from a paid call, and the endpoint uses path parameters that aren't fully documented in the OpenAPI paths entry (uses generic /id placeholder).
Warnings
- —The OpenAPI path uses '/api/flightaware/history/flights/id/route-info' with a generic 'id' placeholder rather than a proper path parameter definition — callers must substitute the actual fa_flight_id in the URL path.
- —No example response from an actual paid call was captured; the example_response_json is inferred from the schema.
Citations
- —Endpoint price is $0.08 per requesthttps://stabletravel.dev/openapi.json
- —Payment is via USDC on Tempo (chainId 4217) with MPP method=tempo, intent=chargehttps://stabletravel.dev/openapi.json
- —Response includes route_distance and fixes array with name, type, latitude, longitudehttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Typical workflow: look up historical flights by ident, then use fa_flight_id for track/route-infohttps://stabletravel.dev/openapi.json