Get a PNG map image of a historical flight track via FlightAware, pay-per-request at $0.28.
What it does
This endpoint returns a PNG map image showing the track of a historical flight, identified by its FlightAware fa_flight_id. It is part of the StableTravel API suite, which wraps FlightAware AeroAPI data behind a pay-per-request MPP/x402 micropayment wall. No API keys or subscriptions are required — payment (USDC on Tempo L2) serves as authentication.
The endpoint accepts optional query parameters to control the rendered image: height and width (pixels), layer_on/layer_off (map layer toggles), show_data_block, airports_expand_view, and show_airports. The response is a PNG image. The price per call is $0.28 USD, settled via the Tempo method on chain ID 4217.
Typical workflow: first call `/api/flightaware/history/flights/{ident}` to retrieve historical flights and obtain a fa_flight_id, then use that ID in this endpoint's path to render the map. The endpoint is live and returns a 402 MPP challenge when called without payment headers.
Capabilities
Use cases
- —Generating a visual map of a past flight's route for a trip report
- —Embedding historical flight track images in dashboards or notifications
- —Providing visual proof of a flight path for expense or insurance claims
- —Displaying past flight routes in travel-planning agent UIs
- —Archiving flight track maps for aviation research
Fit
Best for
- —AI agents that need visual flight history without managing FlightAware credentials
- —Travel apps embedding historical flight maps on-demand
- —Autonomous workflows that pay per image without subscription overhead
Not for
- —Real-time live flight tracking maps (use /api/flightaware/flights/{id}/map instead)
- —Bulk batch rendering of thousands of maps (per-call cost adds up quickly)
- —Applications needing vector/SVG output rather than raster PNG
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/flights/UAL123-1234567890-schedule-0000/map?width=800&height=600"Endpoint
Quality
Full OpenAPI schema present with clear pricing, documented parameters, and a live 402 MPP challenge confirming the endpoint is operational. Response schema is empty (image/PNG), and no example response body is possible for binary content, which slightly limits completeness.
Warnings
- —Response is a PNG image; the OpenAPI response schema is empty/untyped
- —No explicit content-type: image/png declared in the OpenAPI spec (listed as application/json but actually returns PNG)
Citations
- —Price per call is $0.28 USDhttps://stabletravel.dev/openapi.json
- —Endpoint uses MPP Tempo method on chain ID 4217 with intent=chargehttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Tempo serves as authenticationhttps://stabletravel.dev
- —Typical workflow: history/flights/{ident} to get fa_flight_id, then /maphttps://stabletravel.dev/openapi.json