Real-time flight position lookup via FlightAware AeroAPI, pay-per-request at $0.02 per call.
What it does
This endpoint returns the latest known position for a specific flight identified by its FlightAware `fa_flight_id`. It is part of the StableTravel API, which wraps FlightAware's AeroAPI behind an MPP/x402 micropayment layer. The response includes latitude, longitude, altitude, groundspeed, heading, altitude change direction, timestamp, and update type — everything needed to plot a flight's current location on a map or feed into an operational dashboard.
The endpoint costs $0.02 per request, payable via USDC on Tempo (chain ID 4217) or x402. No API keys, OAuth tokens, or subscriptions are required; payment serves as authentication. The typical workflow is: first look up a flight by ident using `/api/flightaware/flights/{ident}` to obtain the `fa_flight_id`, then call this position endpoint with that ID. For a full track history rather than just the latest point, use the sibling `/api/flightaware/flights/{id}/track` endpoint ($0.024).
StableTravel is operated by Merit Systems and exposes a comprehensive OpenAPI 3.1 spec at `https://stabletravel.dev/openapi.json`. The endpoint was confirmed live via a 402 MPP challenge during probing.
Capabilities
Use cases
- —Display a flight's current position on a live map
- —Build an arrival-time estimator by polling position updates
- —Feed flight coordinates into logistics or ground-transport scheduling
- —Monitor fleet positions for airline operations dashboards
- —Trigger alerts when a flight enters a geographic region
Fit
Best for
- —Agents that need a single latest-position snapshot for a known flight
- —Operational tools tracking specific flights by fa_flight_id
- —Low-cost, no-signup flight position queries from autonomous agents
Not for
- —Bulk surveillance of all airborne flights (use the search/positions endpoint instead)
- —Historical track replay (use the /track or /history endpoints)
- —Flight booking or pricing (use the Amadeus-backed endpoints on the same API)
Quick start
# 1. Get the fa_flight_id for a flight
npx agentcash fetch "https://stabletravel.dev/api/flightaware/flights/UAL123"
# 2. Use the fa_flight_id to get latest position
npx agentcash fetch "https://stabletravel.dev/api/flightaware/flights/UAL123-1718000000-airline-0001/position"Example
Response
{
"heading": 270,
"altitude": 370,
"latitude": 40.6413,
"longitude": -73.7781,
"timestamp": "2025-06-15T14:32:00Z",
"groundspeed": 485,
"update_type": "adsb",
"fa_flight_id": "UAL123-1718000000-airline-0001",
"altitude_change": "level"
}Endpoint
Quality
Full OpenAPI 3.1 schema with response types, clear pricing in x-payment-info, live 402 MPP challenge confirmed, and extensive guidance docs. Docked slightly because no worked example response is provided in the spec and the endpoint path uses a generic :id placeholder without explicit path-parameter definition.
Warnings
- —The {id} path parameter is a FlightAware fa_flight_id, not a flight number — callers must first resolve an ident to an fa_flight_id via the /flights/{ident} endpoint.
- —The MPP challenge currency address (0x20c000000000000000000000b9537d11c60e8b50) differs from the OpenAPI x-payment-info currency (0x20c0000000000000000000000000000000000001); the live challenge may reflect a different token contract on Tempo.
Citations
- —Endpoint price is $0.02 per requesthttps://stabletravel.dev/openapi.json
- —Payment via USDC on Tempo (chain ID 4217) with MPP methodhttps://stabletravel.dev/openapi.json
- —Response includes fa_flight_id, altitude, groundspeed, heading, latitude, longitude, timestamp, update_typehttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via x402/MPP serves as authenticationhttps://stabletravel.dev
- —Endpoint confirmed live via 402 MPP challengehttps://stabletravel.dev/api/flightaware/flights/:id/position
- —Operated by Merit Systemshttps://stabletravel.dev/openapi.json