Get filed route fixes and waypoints for a flight via FlightAware AeroAPI at $0.02/request.
What it does
This endpoint returns the filed route information for a specific flight, identified by its FlightAware `fa_flight_id`. The response includes the total route distance and an array of fixes (waypoints) along the route, each with a name, type, latitude, and longitude. It is part of the StableTravel platform, which proxies FlightAware AeroAPI data through a pay-per-request MPP/x402 micropayment interface — no API keys or subscriptions required.
The endpoint accepts GET requests at `/api/flightaware/flights/{id}/route-info`, where `{id}` is a FlightAware flight ID (obtained from other FlightAware endpoints such as `/flights/{ident}`). The price is $0.02 per call, settled via USDC on Tempo (chainId 4217). The OpenAPI schema documents the response as an object with a required `fixes` array and an optional `route_distance` number. Each fix object contains `name`, `type`, `latitude`, and `longitude` fields.
This endpoint is useful for aviation analytics, flight plan visualization, ATC route analysis, and building navigation-aware applications. It complements the related `/flights/{id}/track` endpoint (which returns actual position history) by providing the planned/filed route instead. The endpoint is confirmed live via a 402 MPP challenge response.
Capabilities
Use cases
- —Retrieve the filed ATC route and waypoints for a specific in-progress or recent flight
- —Visualize a flight's planned route on a map by plotting fix coordinates
- —Compare filed route fixes against actual track positions for deviation analysis
- —Build aviation dashboards that display planned routing for monitored flights
- —Feed route waypoint data into autonomous travel-planning agents
Fit
Best for
- —Agents or apps that need planned flight route geometry (not just actual track)
- —Aviation analytics requiring named fixes and waypoint types along a route
- —Developers who want FlightAware AeroAPI data without managing API keys or subscriptions
Not for
- —Getting real-time aircraft position — use the /track or /position endpoints instead
- —Booking flights or searching for flight offers — use the Amadeus or Google Flights endpoints on StableTravel
Quick start
# Get route info for a flight (replace FA_FLIGHT_ID with an actual fa_flight_id)
npx agentcash fetch "https://stabletravel.dev/api/flightaware/flights/UAL123-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.45,
"longitude": -74.12
},
{
"name": "KLAX",
"type": "Destination",
"latitude": 33.9425,
"longitude": -118.4081
}
],
"route_distance": 2475
}Endpoint
Quality
Full OpenAPI 3.1 schema with response structure documented, live 402 MPP challenge confirmed, clear pricing ($0.02/call), and comprehensive guidance docs. Slightly below 0.9 because no real example response was captured (only schema-inferred) and the endpoint uses path parameters that aren't fully parameterized in the OpenAPI spec.
Warnings
- —The example response is inferred from the schema, not captured from a live call.
- —The path parameter :id (fa_flight_id) is not explicitly documented with examples in the OpenAPI spec for this specific endpoint — callers must first obtain an fa_flight_id from another FlightAware endpoint.
Citations
- —Endpoint price is $0.02 per requesthttps://stabletravel.dev/openapi.json
- —Response schema includes fixes array with name, type, latitude, longitude and optional route_distancehttps://stabletravel.dev/openapi.json
- —Payment is via MPP method tempo with intent charge on chainId 4217https://stabletravel.dev/openapi.json
- —Endpoint is live, confirmed by 402 MPP challenge responsehttps://stabletravel.dev/api/flightaware/flights/:id/route-info
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev