Pay-per-call airline and airport IATA code lookup via MPP on Tempo L2.
What it does
FlightAPI's IATA endpoint provides airline and airport code lookups, settling payments through the Tempo L2 network using the MPP (Micropayment Protocol). The endpoint is live and returns a standard 402 Payment Required challenge, indicating it accepts per-call charges settled in pathUSD on chain ID 4217. The price per request is 2000 base units of pathUSD (pathUSD uses 6 decimals), which works out to $0.002 per call.
The endpoint path pattern `/iata/:rest*` suggests a RESTful design where you supply an IATA code (airline or airport) as a path parameter. It is part of a broader FlightAPI suite described as offering real-time flight prices, tracking, and airport schedules from 700+ airlines, though this specific endpoint is scoped to code lookups only.
Documentation is extremely sparse — the provider's root, /docs, /api, /pricing, and /README all return 404. There is no OpenAPI schema, no usage examples, and no detailed response format available. The endpoint is confirmed live via the MPP 402 challenge, but consumers will need to experiment with path parameters to determine exact request/response shapes. The fee payer flag is set to true, meaning the provider covers transaction fees on the Tempo chain.
Capabilities
Use cases
- —Resolving IATA codes to airline or airport names in travel applications
- —Validating airline/airport codes during booking flows
- —Enriching flight data pipelines with standardized IATA identifiers
- —Building agent-driven travel planners that need code lookups on demand
Fit
Best for
- —AI agents needing on-demand airline/airport code resolution
- —Micropayment-friendly travel data lookups
- —Applications already integrated with Tempo L2 / MPP wallets
Not for
- —Bulk or batch IATA data downloads (pay-per-call model would be costly at scale)
- —Use cases requiring full flight tracking or pricing (this endpoint is code lookup only)
- —Teams without an MPP-compatible wallet or Tempo L2 integration
Quick start
# Probe the endpoint to receive the MPP 402 challenge
curl -i https://flightapi.mpp.tempo.xyz/iata/JFK
# Returns 402 with WWW-Authenticate: Payment header.
# Sign and attach a Tempo L2 payment proof to complete the request.Endpoint
Quality
The endpoint is confirmed live via a valid MPP 402 challenge with clear pricing, but there is zero documentation, no OpenAPI schema, no response examples, and no crawlable content. Nearly everything beyond the challenge itself must be inferred from the endpoint path and existing title/description.
Warnings
- —No documentation found — root, /docs, /api, /pricing, /README all return 404.
- —No OpenAPI or response schema available; request/response format is unknown.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 on chain 4217 is assumed to be pathUSD (6 decimals) but could not be independently verified.
- —Exact path parameter format (airline vs. airport codes, 2-letter vs. 3-letter) is undocumented.
Citations
- —Endpoint returns HTTP 402 with MPP challenge using method 'tempo', intent 'charge', on chain 4217https://flightapi.mpp.tempo.xyz/iata/:rest*
- —Price per call is 2000 base units; recipient is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fehttps://flightapi.mpp.tempo.xyz/iata/:rest*
- —Part of FlightAPI suite described as real-time flight prices, tracking, and airport schedules from 700+ airlineshttps://flightapi.mpp.tempo.xyz/iata/:rest*