Look up historical flights by ident via FlightAware AeroAPI — $0.04/request, pay with USDC on Tempo.
What it does
This endpoint returns historical flight data for a given flight ident (designator, registration, or fa_flight_id) through FlightAware's AeroAPI, proxied by StableTravel. It is a GET request to `/api/flightaware/history/flights/:id` where `:id` is the flight identifier. The response includes an array of past flights with origin/destination airport details (ICAO/IATA codes, city, name), scheduled and actual gate/runway times, delays, aircraft type, filed route, altitude, airspeed, route distance, gate and terminal info, and pagination cursors for large result sets.
The endpoint costs $0.04 per request. Payment is handled automatically via the MPP protocol using USDC (pathUSD) on the Tempo L2 chain (chainId 4217). No API keys or accounts are required — the micropayment serves as authentication. Optional query parameters include `ident_type` (fa_flight_id, designator, or registration), `start` and `end` ISO 8601 timestamps to filter the time range, `max_pages`, and a `cursor` for pagination.
This is one endpoint within the broader StableTravel platform, which offers 60+ pay-per-request travel endpoints covering Amadeus GDS (flights, hotels, activities, transfers), FlightAware (real-time tracking, airport info, history, disruptions), and Google Flights (price comparison). A typical workflow for flight history research is to call this endpoint first to get `fa_flight_id` values, then drill into `/history/flights/{id}/track` for position data or `/history/flights/{id}/map` for a PNG track image.
Capabilities
Use cases
- —Retrieve past flights for a specific flight number to analyze on-time performance
- —Look up historical operations for an aircraft registration to audit utilization
- —Research route history for a designator over a date range
- —Feed historical flight data into delay-prediction or analytics pipelines
- —Verify past flight details (times, airports, aircraft) for expense or compliance reporting
Fit
Best for
- —Agents that need historical aviation operational data without managing FlightAware API keys
- —Autonomous travel-planning agents that research route reliability before booking
- —Analytics workflows that consume flight history in small, pay-as-you-go increments
Not for
- —Real-time flight tracking (use the /flightaware/flights/{ident} or /flights/{id}/track endpoints instead)
- —Booking flights (use the Amadeus /flights/search → /flights/book workflow)
- —Bulk historical data exports requiring millions of records at once
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/flights/UAL100?start=2025-01-01T00:00:00Z&end=2025-01-31T23:59:59Z"Example
Response
{
"links": {
"next": null
},
"flights": [
{
"ident": "UAL100",
"origin": {
"city": "Newark",
"code": "KEWR",
"name": "Newark Liberty Intl",
"code_iata": "EWR"
},
"status": "Arrived",
"operator": "UAL",
"actual_in": "2025-01-16T10:20:00Z",
"actual_out": "2025-01-15T22:45:00Z",
"ident_iata": "UA100",
"destination": {
"city": "London",
"code": "EGLL",
"name": "London Heathrow",
"code_iata": "LHR"
},
"fa_flight_id": "UAL100-1735689600-airline-0123",
"scheduled_in": "2025-01-16T10:30:00Z",
"aircraft_type": "B772",
"arrival_delay": -600,
"scheduled_out": "2025-01-15T22:30:00Z",
"route_distance": 3459,
"departure_delay": 900
}
],
"num_pages": 1
}Endpoint
Quality
Full OpenAPI 3.1 schema with response types, clear pricing ($0.04/call), live 402 MPP challenge captured, comprehensive guidance docs, and detailed parameter descriptions. Slightly below 0.9 because no inline response examples are provided in the spec and the example response above is synthesized from the schema.
Warnings
- —Example response JSON is synthesized from the OpenAPI schema, not captured from a live call.
- —The endpoint URL uses a path parameter (:id) but the OpenAPI spec lists the path as /api/flightaware/history/flights/id — callers must replace the literal 'id' segment with the actual flight ident.
Citations
- —Endpoint price is $0.04 per requesthttps://stabletravel.dev/openapi.json
- —Payment via MPP protocol using Tempo method (chainId 4217) with pathUSD currencyhttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Typical workflow: /flightaware/history/flights/{ident} → /flightaware/history/flights/{id}/trackhttps://stabletravel.dev/openapi.json
- —MPP 402 challenge is live with intent=charge and method=tempohttps://stabletravel.dev/api/flightaware/history/flights/:id