Multi-city flight price search across 700+ airlines, pay-per-call via Tempo L2.
What it does
FlightAPI's multi-trip endpoint provides real-time multi-city flight price searches. It is part of a broader FlightAPI suite offering flight prices, tracking, and airport schedules from over 700 airlines. The endpoint is accessed via a REST-style path (multitrip/:rest*) and settles payments on Tempo L2 (chain ID 4217) using pathUSD at $0.008 per request.
The endpoint uses the MPP (Micropayment Protocol) with a charge-per-call intent, meaning each request is independently paid. The fee payer flag is set to true, so the provider covers gas fees for the payment transaction. This makes it straightforward for agents to call without needing to manage on-chain gas.
Documentation is not available at the provider's origin (all crawled paths return 404), so the exact request parameters and response schema are unknown. Based on the endpoint path pattern and description, it likely accepts origin/destination pairs and dates for multi-leg itineraries and returns pricing data. Users should expect to supply route segments as path parameters or query strings under the :rest* wildcard.
Capabilities
Use cases
- —Building a travel agent that finds optimal multi-city itineraries
- —Comparing multi-leg flight prices across carriers for trip planning tools
- —Automating complex travel booking workflows that require multi-stop routing
Fit
Best for
- —AI travel agents needing real-time multi-city fare data
- —Applications requiring pay-per-use flight pricing without subscriptions
- —Developers building multi-destination trip planners
Not for
- —Simple one-way or round-trip searches (other FlightAPI endpoints may be more appropriate)
- —Bulk historical fare analysis requiring thousands of free queries
- —Flight booking or ticketing (this is search/pricing only)
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://flightapi.mpp.tempo.xyz/multitrip/SFO/LAX/JFK/2025-06-01/2025-06-05"Endpoint
Quality
The endpoint is confirmed live via a valid 402 MPP challenge with clear pricing, but no documentation, OpenAPI schema, or example responses are available. The request format and response structure must be guessed from the path pattern.
Warnings
- —No documentation found at provider origin — all crawled paths return 404
- —Request parameters and response schema are entirely unknown
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD (6 decimals) based on Tempo L2 context; if different, price calculation may be wrong
Citations
- —Part of FlightAPI suite covering 700+ airlines with flight prices, tracking, and airport scheduleshttps://flightapi.mpp.tempo.xyz/multitrip/:rest*
- —Price is 8000 base units on chain 4217 with fee payer enabledhttps://flightapi.mpp.tempo.xyz/multitrip/:rest*