Track flights between airports via pay-per-call API on Tempo L2
What it does
FlightAPI's Track-by-Route endpoint lets you look up flights operating between two airports. It is part of a broader FlightAPI suite offering real-time flight prices, tracking, and airport schedules covering 700+ airlines. The endpoint is accessed via a simple GET request with route parameters specifying origin and destination airports.
Payment is handled through the MPP (Micropayment Protocol) using the Tempo method on chain ID 4217. Each call costs 2000 base units of pathUSD (6 decimals), which equates to $0.002 per request. The provider covers transaction fees (feePayer: true), so callers only pay the stated amount. Settlement goes to the recipient address on Tempo L2.
No OpenAPI schema or documentation pages were found on the endpoint's domain. The endpoint is confirmed live, returning a proper 402 Payment Required challenge. The URL pattern `/trackbyroute/:rest*` suggests route parameters are passed as path segments (likely origin and destination airport codes), but exact parameter format is undocumented in available materials.
Capabilities
Use cases
- —Look up active flights between two specific airports
- —Monitor flight availability on a given route
- —Build travel apps that show current flights between city pairs
- —Integrate real-time route-level flight data into agent workflows
- —Compare airline coverage between airport pairs
Fit
Best for
- —Agents needing programmatic flight route lookups
- —Travel automation workflows requiring per-call pricing
- —Developers building airport-pair flight dashboards
Not for
- —Bulk historical flight data analysis (no batch endpoint documented)
- —Flight booking or ticket purchasing
- —Detailed individual flight tracking by flight number (separate endpoint likely exists)
Quick start
curl -X GET "https://flightapi.mpp.tempo.xyz/trackbyroute/JFK/LAX" \
-H "Authorization: Payment <tempo-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 MPP challenge, but no documentation, OpenAPI schema, or example responses are available. URL parameter format and response structure are entirely inferred from the endpoint path pattern and existing description.
Warnings
- —No documentation or OpenAPI schema found — parameter format and response structure are unknown
- —Root domain returns 404; no docs, pricing, or README pages available
- —Currency contract address could not be independently verified; price assumed to be pathUSD with 6 decimals based on Tempo L2 conventions
Citations
- —Part of FlightAPI covering 700+ airlines with real-time flight prices, tracking, and airport scheduleshttps://flightapi.mpp.tempo.xyz/trackbyroute/:rest*
- —Endpoint is live and returns 402 Payment Required with MPP Tempo challengehttps://flightapi.mpp.tempo.xyz/trackbyroute/:rest*
- —Amount is 2000 base units on chain 4217 with feePayer truehttps://flightapi.mpp.tempo.xyz/trackbyroute/:rest*