Pay-per-call round-trip flight price search via MPP on Tempo L2
What it does
FlightAPI's round-trip endpoint provides real-time round-trip flight price searches across 700+ airlines. It is accessed via the Micropayment Protocol (MPP) and settles payments on the Tempo L2 chain (chainId 4217). Each call costs 3000 base units of pathUSD (the Tempo L2 stablecoin with 6 decimals), which equals $0.003 per request. The provider covers gas fees (feePayer: true), so callers only pay the per-call charge.
The endpoint follows a REST-style path pattern at `/roundtrip/:rest*`, suggesting that flight search parameters (origin, destination, dates, passengers, cabin class, etc.) are passed as path segments or query parameters. However, no OpenAPI schema, documentation pages, or usage examples were found during crawling — the provider's root domain and common doc paths all return 404. The endpoint itself is confirmed live: it returns a well-formed 402 Payment Required challenge with a valid WWW-Authenticate header, indicating it is ready to accept paid requests.
Because no request/response schema is published, callers will need to experiment with the path structure or obtain documentation from the FlightAPI provider directly. The listing description mentions coverage of 700+ airlines and capabilities including real-time prices, tracking, and airport schedules, though only the round-trip price search function is exposed at this specific endpoint.
Capabilities
Use cases
- —AI travel agents searching for round-trip flight prices on behalf of users
- —Automated fare comparison across 700+ airlines
- —Building trip-planning tools that need real-time airfare data
- —Programmatic monitoring of round-trip flight prices for specific routes
Fit
Best for
- —Agents needing on-demand round-trip flight pricing without subscription commitments
- —Low-volume or bursty flight search workloads where pay-per-call is cost-effective
- —Crypto-native applications that can settle via Tempo L2
Not for
- —High-volume fare aggregation requiring bulk/subscription pricing
- —Applications that cannot interact with MPP or Tempo L2 payment rails
- —One-way or multi-city flight searches (this endpoint is specifically round-trip)
Quick start
# 1. GET the endpoint to receive the 402 challenge
curl -i https://flightapi.mpp.tempo.xyz/roundtrip/JFK/LAX/2025-08-01/2025-08-10/1
# 2. Parse the WWW-Authenticate header, sign a Tempo L2 payment for 3000 base units of pathUSD
# 3. Re-send the request with the Authorization: Payment header attachedEndpoint
Quality
The endpoint is confirmed live via a valid 402 MPP challenge, and pricing is clear ($0.003 per call on Tempo L2). However, no documentation, OpenAPI schema, request/response examples, or even a working landing page were found. The path pattern and parameter structure must be inferred or obtained externally, making this effectively a stub listing.
Warnings
- —No API documentation or OpenAPI schema found — all doc paths return 404
- —Request path structure (/roundtrip/:rest*) is undocumented; parameter format is unknown
- —No response schema available; output format must be discovered empirically
- —Currency address 0x20c0...8b50 on chainId 4217 is assumed to be pathUSD (6 decimals) but could not be independently verified
Citations
- —Part of FlightAPI covering 700+ airlines with real-time flight prices, tracking, and airport scheduleshttps://flightapi.mpp.tempo.xyz/roundtrip/:rest*
- —Endpoint returns a valid 402 MPP challenge with method=tempo, intent=charge, amount=3000, chainId=4217, feePayer=truehttps://flightapi.mpp.tempo.xyz/roundtrip/:rest*