Look up real-time flight information by flight number, paid per call via Tempo L2.
What it does
This MPP endpoint returns flight information when queried by flight number. It is part of the GoFlightLabs suite, which provides real-time flight tracking, pricing, schedules, and airline data. The endpoint is live and settles payments on Tempo L2 (chain ID 4217) using the pathUSD stablecoin at $0.005 (5000 base units, 6 decimals) per request.
The endpoint uses the MPP (Micropayment Protocol) with a "charge" intent, meaning each call is a one-shot payment. The fee payer flag is set to true, so the provider covers transaction fees on the Tempo chain. No OpenAPI schema or documentation pages were found on the provider's domain, so the exact request parameters and response shape must be inferred from the endpoint path and description. Typically, flight-info-by-flight-number endpoints accept a flight number (e.g., "AA100") as a query parameter and return details such as departure/arrival airports, times, status, aircraft type, and airline information.
Because no documentation, schema, or example responses are available from the crawled pages, the precise query parameter names and response fields are unknown. Users should experiment with common parameter names like `flight_number` or `flightNumber` as a GET query parameter. The endpoint is confirmed live via its 402 challenge response.
Capabilities
Use cases
- —Retrieve current status and details for a specific flight by its flight number
- —Build travel assistant agents that provide real-time flight updates
- —Integrate flight information into booking or itinerary management workflows
- —Power notification systems that alert users about flight delays or gate changes
Fit
Best for
- —AI agents needing on-demand flight information without API key management
- —Micropayment-based access to flight data without subscription commitments
- —Developers building travel tools who want pay-per-call pricing
Not for
- —Bulk historical flight data analysis (per-call pricing would be expensive at scale)
- —Applications requiring detailed airport or route databases rather than per-flight lookups
Quick start
curl -X GET "https://goflightlabs.mpp.tempo.xyz/flight-info-by-flight-number?flight_number=AA100" \
-H "Authorization: Payment <tempo-payment-token>"Endpoint
Quality
The endpoint is confirmed live via its 402 MPP challenge, and pricing is clear ($0.005/call on Tempo L2). However, no documentation, OpenAPI schema, or example responses were found—all crawled pages returned 404. Request parameters and response format are entirely inferred.
Warnings
- —No documentation or schema available; all crawled pages return 404.
- —Request parameter names (e.g., flight_number) are guessed—actual parameter names are unknown.
- —Response format and fields are unknown; no example response is available.
- —Currency address 0x20c0…8b50 is assumed to be pathUSD (6 decimals) based on Tempo L2 conventions but could not be independently verified.
Citations
- —The endpoint is live and returns a 402 MPP challenge with method=tempo, intent=charge, amount=5000 on chain 4217.https://goflightlabs.mpp.tempo.xyz/flight-info-by-flight-number
- —Part of GoFlightLabs: Real-time flight tracking, prices, schedules, and airline data.https://goflightlabs.mpp.tempo.xyz/flight-info-by-flight-number