Real-time flight data via pay-per-call MPP endpoint on Tempo L2
What it does
AviationStack Real-time Flights is an MPP (Micropayment Protocol) endpoint that provides real-time flight tracking data. It is hosted at aviationstack.mpp.tempo.xyz and settles payments via the Tempo method on chain ID 4217. Each API call costs 5000 base units of pathUSD (0.005 USD per request, assuming 6-decimal pathUSD), making it suitable for lightweight, per-query consumption by AI agents or automated systems.
The endpoint responds to GET requests at /v1/flights and is part of the broader AviationStack suite, which traditionally offers real-time and historical flight tracking, airport data, airline information, and flight schedules. However, the MPP-wrapped version provides no public documentation, OpenAPI schema, or landing page — all auxiliary routes (docs, pricing, README) return 404. The only confirmed capability is the /v1/flights path returning a valid 402 payment challenge.
Because no schema or response examples are available from the provider, the exact query parameters and response format must be inferred from the upstream AviationStack API (which typically accepts parameters like flight_iata, airline_name, dep_iata, arr_iata, flight_status, etc.). Users should expect JSON responses containing flight objects with departure/arrival details, airline info, and live tracking data, but this is not confirmed from the MPP proxy itself.
Capabilities
Use cases
- —AI agents querying live flight status for travel planning or customer support
- —Automated monitoring of specific flight arrivals and departures
- —Building travel dashboards that pull real-time flight data on demand
- —Chatbots answering user questions about current flight positions or delays
Fit
Best for
- —Agents needing per-call flight data without subscription commitments
- —Crypto-native applications settling micropayments on Tempo L2
- —Low-volume or bursty flight data lookups where pay-per-call is cost-effective
Not for
- —High-volume bulk flight data ingestion (per-call cost adds up)
- —Use cases requiring historical flight data or schedules (only /v1/flights confirmed)
- —Users who need detailed API documentation before integrating
Quick start
# Pay-per-call via MPP on Tempo L2
curl -X GET "https://aviationstack.mpp.tempo.xyz/v1/flights?flight_iata=AA100" \
-H "Authorization: Payment <tempo-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid 402 MPP challenge, confirming it accepts payments and serves data. However, there is no documentation, no OpenAPI schema, no response examples, and all auxiliary pages return 404. Query parameters and response format are entirely inferred from the upstream AviationStack API. The currency contract address is non-standard and cannot be definitively mapped to a known token, adding pricing uncertainty.
Warnings
- —No documentation, OpenAPI schema, or landing page available — all auxiliary routes return 404
- —Currency contract address 0x20c000000000000000000000b9537d11c60e8b50 is not a well-known token; price of 5000 base units assumes 6-decimal pathUSD ($0.005) but this is unconfirmed
- —Query parameters and response format are inferred from upstream AviationStack API, not confirmed by this MPP proxy
- —No examples of successful (200) responses are available
Citations
- —Endpoint returns a valid 402 MPP challenge with method=tempo, intent=charge, amount=5000, chainId=4217https://aviationstack.mpp.tempo.xyz/v1/flights
- —Part of AviationStack suite offering real-time and historical flight tracking, airports, airlines, and scheduleshttps://aviationstack.mpp.tempo.xyz/v1/flights