Look up real-time flight data by airline callsign, paid per request via Tempo L2.
What it does
The GoFlightLabs Flights-by-Callsign endpoint lets you query flight information using an airline callsign. It is part of the broader GoFlightLabs suite, which provides real-time flight tracking, pricing, schedules, and airline data. The endpoint is accessed via a simple GET request and is monetized through the MPP (Micropayment Protocol) using the Tempo settlement method.
Each request costs 5,000 base units of the payment token on Tempo chain (chainId 4217). The exact token is identified by the currency address 0x20c000000000000000000000b9537d11c60e8b50; assuming 6 decimals (typical for stablecoins on Tempo/pathUSD), this works out to $0.005 per call. The provider covers gas fees (feePayer: true), so the caller only pays the data cost. Settlement is one-shot (intent: charge) — each API call is independently paid.
No OpenAPI schema, documentation pages, or usage examples were found on the MPP gateway. The endpoint is confirmed live (returns a valid 402 Payment Required challenge), but without schema details the exact query parameters and response format remain unknown. Callers should expect to pass a callsign identifier (likely as a query parameter such as `?callsign=<VALUE>`) and receive JSON flight data in return. For authoritative parameter and response documentation, refer to the upstream GoFlightLabs API docs at goflightlabs.com.
Capabilities
Use cases
- —Retrieve current flight status and position for a specific airline callsign
- —Build flight-tracking dashboards that resolve callsigns to route and schedule data
- —Power chatbot or agent workflows that answer user questions about specific flights
- —Integrate callsign-based flight lookups into travel planning applications
Fit
Best for
- —Agents or apps that need per-call flight data without a subscription
- —Developers wanting crypto-settled aviation data on Tempo L2
- —Lightweight integrations that look up individual flights by callsign
Not for
- —Bulk historical flight data analysis requiring thousands of calls at once
- —Use cases needing full airport or route search (different GoFlightLabs endpoints exist for those)
- —Users who cannot transact on Tempo L2 or lack pathUSD tokens
Quick start
curl -X GET "https://goflightlabs.mpp.tempo.xyz/flights-callsign?callsign=BAW123" \
-H "Authorization: Payment <tempo-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid 402 MPP challenge, confirming it is operational. However, no documentation, OpenAPI schema, or response examples are available from the crawl. Query parameters and response shape are inferred from the endpoint name and the GoFlightLabs brand description, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation found — request parameters and response format are inferred.
- —Currency token address could not be independently verified; price assumes 6-decimal stablecoin (likely pathUSD). If decimals differ, the per-call cost will be different.
- —Root domain and all documentation paths return 404; no on-site docs available.
Citations
- —Endpoint returns a valid 402 MPP challenge with method=tempo, intent=charge, amount=5000https://goflightlabs.mpp.tempo.xyz/flights-callsign
- —Part of GoFlightLabs: Real-time flight tracking, prices, schedules, and airline datahttps://goflightlabs.mpp.tempo.xyz/flights-callsign