Pay-per-call airport schedule data via MPP on Tempo L2
What it does
FlightAPI Airport Schedule is a pay-per-call API endpoint that returns airport schedule information. It is part of the broader FlightAPI suite, which advertises real-time flight prices, tracking, and airport schedules from 700+ airlines. The endpoint is accessed via the Micropayment Protocol (MPP) and settles payments in pathUSD on the Tempo L2 chain (chainId 4217).
Each call costs 3,000 base units of pathUSD. Assuming pathUSD uses 6 decimals (consistent with other USD stablecoins), this translates to $0.003 per request. The endpoint uses a charge-per-call intent, meaning each request is independently paid. The provider covers gas fees (feePayer: true), so callers only pay the stated amount.
The endpoint pattern is `/schedule/:rest*`, suggesting it accepts path parameters (likely an airport IATA code or similar identifier) to specify which airport's schedule to retrieve. No OpenAPI schema, documentation pages, or example responses were found during crawling — the root domain and all common doc paths return 404. The endpoint itself is confirmed live, returning a proper 402 MPP challenge on unauthenticated GET requests.
Capabilities
Use cases
- —Retrieve departure and arrival schedules for a specific airport
- —Build travel apps that display real-time airport boards
- —Power agent workflows that need to check flight schedules before booking
Fit
Best for
- —AI agents needing on-demand airport schedule data without API key management
- —Micropayment-based travel data consumers on Tempo L2
- —Applications requiring per-call billing with no subscription commitment
Not for
- —Bulk historical flight data analysis (pay-per-call would be expensive at scale)
- —Use cases requiring detailed documentation or guaranteed SLA (no docs available)
Quick start
curl -X GET https://flightapi.mpp.tempo.xyz/schedule/JFK \
-H "Authorization: Payment <signed-tempo-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 MPP challenge, but no documentation, OpenAPI schema, or example responses are available. The URL path pattern and description hint at airport schedule data, but request/response formats are entirely unknown. Pricing is inferrable from the challenge but the currency address is non-standard and decimals are assumed.
Warnings
- —No documentation found — all doc paths return 404
- —No OpenAPI or schema available; request and response formats are unknown
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is not a well-known stablecoin contract; decimals assumed to be 6 (pathUSD convention) but unverified
- —The :rest* path parameter pattern is ambiguous — exact path structure for querying specific airports is undocumented
Citations
- —Part of FlightAPI suite covering real-time flight prices, tracking, and airport schedules from 700+ airlineshttps://flightapi.mpp.tempo.xyz/schedule/:rest*
- —Endpoint returns 402 MPP challenge with method=tempo, intent=charge, amount=3000, chainId=4217https://flightapi.mpp.tempo.xyz/schedule/:rest*