Get a PNG map image of a live flight track via FlightAware for $0.06 per request.
What it does
This endpoint returns a PNG map image showing the flight track for a specific flight, identified by its FlightAware fa_flight_id. It is part of the StableTravel API, which wraps FlightAware's AeroAPI behind a pay-per-request MPP/x402 micropayment wall. The endpoint accepts optional query parameters to control image dimensions (height, width), map layers (layer_on, layer_off), whether to show a data block or airports on the map, and whether to expand the view to include airports. The response is a PNG image. The price is $0.06 per call, settled in pathUSD on Tempo (chain 4217).
StableTravel requires no API keys or subscriptions. Payment via the MPP protocol header serves as authentication. The typical workflow is: look up a flight ident via `/api/flightaware/flights/{ident}` to obtain the `fa_flight_id`, then call this map endpoint with that ID in the URL path. The endpoint is a GET request and is live, confirmed by a 402 MPP challenge response. The full OpenAPI 3.1 spec is published at `/openapi.json` and documents all parameters and pricing.
This endpoint is one of over 60 travel-related endpoints on StableTravel covering flights (Amadeus GDS), hotels, activities, transfers, Google Flights price comparison, and the full FlightAware suite for real-time tracking, airport info, weather, history, and disruption data. All endpoints follow the same pay-per-request model with prices ranging from $0.001 to $0.40.
Capabilities
Use cases
- —Generating a visual map of a live flight's track for display in a travel dashboard or chatbot
- —Embedding flight track images in email or SMS notifications about flight progress
- —Creating visual flight reports for operations teams monitoring specific routes
- —Adding flight path visualizations to travel itinerary documents
Fit
Best for
- —Agents that need a visual flight track image without rendering their own map
- —Quick visual confirmation of a flight's path for end users
- —Embedding flight maps in contexts where interactive maps aren't available
Not for
- —Getting structured position/coordinate data (use the /track endpoint instead)
- —Historical flight maps (use /api/flightaware/history/flights/{id}/map at $0.28)
- —Real-time streaming position updates
Quick start
# First get a fa_flight_id, then fetch the map:
npx agentcash fetch "https://stabletravel.dev/api/flightaware/flights/UAL123" \
# Extract fa_flight_id from response, then:
npx agentcash fetch "https://stabletravel.dev/api/flightaware/flights/<fa_flight_id>/map?width=800&height=600"Endpoint
Quality
Full OpenAPI 3.1 schema with clear pricing, parameters, and endpoint documentation. Live 402 MPP challenge confirmed. Response schema is empty (PNG binary), and no example response can be shown for an image endpoint, which slightly reduces the score.
Warnings
- —Response is a PNG image, not JSON — the OpenAPI response schema is empty
- —The :id path parameter must be a FlightAware fa_flight_id, not a flight number — requires a prior lookup call
Citations
- —Endpoint price is $0.06 per callhttps://stabletravel.dev/openapi.json
- —Payment settled in pathUSD on Tempo chain 4217 via MPP protocolhttps://stabletravel.dev/openapi.json
- —Endpoint is live, confirmed by 402 MPP challengehttps://stabletravel.dev/api/flightaware/flights/:id/map
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Optional parameters include height, width, layer_on, layer_off, show_data_block, airports_expand_view, show_airportshttps://stabletravel.dev/openapi.json
- —Typical workflow: look up flight ident to get fa_flight_id, then call map endpointhttps://stabletravel.dev/docs