Pay-per-call one-way flight price search across 700+ airlines via MPP on Tempo L2.
What it does
FlightAPI's one-way trip endpoint provides real-time one-way flight price searches, covering 700+ airlines. It 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 (pathUSD uses 6 decimals, so this equals $0.003 per request). The endpoint uses a charge-per-call model, meaning each request is independently paid for.
The endpoint URL pattern is `https://flightapi.mpp.tempo.xyz/onewaytrip/:rest*`, where the `:rest*` wildcard segment likely encodes route parameters such as origin airport, destination airport, and travel date. No OpenAPI schema or documentation pages were found on the provider's domain, so the exact parameter format and response structure must be inferred or discovered through experimentation. The provider's own description states it is part of a broader FlightAPI suite offering real-time flight prices, tracking, and airport schedules.
The MPP challenge is live and well-formed, with an expiry date of April 2026, indicating the service is actively maintained. The fee payer flag is set to true, meaning the endpoint provider covers the on-chain transaction fee for settlement. No authentication beyond the MPP payment is documented. Because no docs, OpenAPI spec, or example responses were found, users should expect to experiment with URL path conventions (e.g., IATA codes and date formats) to construct valid queries.
Capabilities
Use cases
- —AI travel agents searching for one-way flight prices on behalf of users
- —Automated fare comparison across 700+ airlines
- —Building trip-planning tools that need real-time one-way flight quotes
- —Programmatic monitoring of flight prices for specific routes
- —Agent-driven itinerary construction with live pricing
Fit
Best for
- —AI agents that need pay-per-call flight pricing without API key signup
- —One-way trip fare lookups across a large airline network
- —Developers building travel tools who want crypto-micropayment-based access
Not for
- —Round-trip or multi-city flight searches (this endpoint is one-way only)
- —Users who need detailed documentation or OpenAPI specs before integrating
- —High-volume bulk fare scraping where per-call costs may accumulate
Quick start
# MPP charge-per-call: GET with payment header
# Price: $0.003 per call (3000 base units pathUSD, 6 decimals)
curl -X GET \
'https://flightapi.mpp.tempo.xyz/onewaytrip/JFK/LAX/2025-08-01' \
-H 'Authorization: Payment <signed-tempo-payment-token>'Endpoint
Quality
The MPP challenge is live and well-formed, confirming the endpoint exists and pricing is clear ($0.003/call). However, no documentation, OpenAPI schema, example requests/responses, or even a working landing page were found. The URL path parameter format is entirely inferred. This is effectively a stub listing.
Warnings
- —No documentation or OpenAPI schema found — all crawled pages returned 404
- —URL path parameter format (airports, dates) is unknown and must be discovered experimentally
- —Currency address 0x20c0...8b50 on chainId 4217 is assumed to be pathUSD with 6 decimals based on Tempo conventions; if decimals differ, the stated price would be wrong
- —Response schema is completely unknown
Citations
- —Part of FlightAPI covering 700+ airlines with real-time flight prices, tracking, and airport scheduleshttps://flightapi.mpp.tempo.xyz/onewaytrip/:rest*
- —MPP challenge returns 402 with method=tempo, intent=charge, amount=3000, chainId=4217https://flightapi.mpp.tempo.xyz/onewaytrip/:rest*