Retrieve airport data via pay-per-call API settled on Tempo L2.
What it does
GoFlightLabs Retrieve Airports is an MPP (Micropayment Protocol) endpoint that returns airport information on a per-call payment basis. It is part of the broader GoFlightLabs suite, which provides real-time flight tracking, pricing, schedules, and airline data. Each call is settled via the Tempo method on chain ID 4217 (Tempo L2) using pathUSD.
The endpoint is live and responds with a standard 402 Payment Required challenge. The per-call cost is 5,000 base units of pathUSD. Assuming pathUSD uses 6 decimals (consistent with other USD-pegged stablecoins on Tempo), this translates to $0.005 (half a cent) per request. The provider covers gas fees (feePayer: true), so callers only pay the data fee.
Documentation is extremely sparse — the provider's MPP subdomain returns 404 on all common documentation paths (/docs, /api, /pricing, /README). The endpoint name and description strongly suggest it returns a list or lookup of airports, likely including fields such as IATA/ICAO codes, airport names, locations, and country information, but the exact request parameters and response schema are not documented in any available material.
Capabilities
Use cases
- —Looking up airport details (codes, names, locations) for travel applications
- —Enriching flight search or booking tools with airport metadata
- —Building aviation dashboards that need structured airport reference data
Fit
Best for
- —Agents needing on-demand airport reference data without API key management
- —Low-volume airport lookups where pay-per-call is more economical than a subscription
- —Crypto-native applications that can settle micropayments on Tempo L2
Not for
- —High-volume bulk airport data ingestion (per-call cost adds up)
- —Users who need comprehensive documentation or guaranteed SLA before integrating
Quick start
curl -i https://goflightlabs.mpp.tempo.xyz/retrieve-airports
# Returns 402 with WWW-Authenticate: Payment header.
# Parse the challenge, sign a Tempo payment of 5000 pathUSD base units,
# then replay the request with the Authorization: Payment header.Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is parseable, but there is zero documentation: no OpenAPI schema, no parameter descriptions, no example responses, and all doc paths return 404. The listing is effectively a stub inferred from the endpoint name and MPP challenge alone.
Warnings
- —No documentation available — all common doc paths return 404.
- —Request parameters and response schema are entirely unknown; the endpoint name is the only clue to functionality.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals; if decimals differ, the stated price ($0.005) would be incorrect.
- —Root domain returns 404, so there is no landing page or usage guide.
Citations
- —Endpoint is live and returns a 402 MPP challenge with method=tempo, intent=charge, amount=5000https://goflightlabs.mpp.tempo.xyz/retrieve-airports
- —Part of GoFlightLabs which provides real-time flight tracking, prices, schedules, and airline datahttps://goflightlabs.mpp.tempo.xyz/retrieve-airports