Pay-per-call flight delay information via MPP on Tempo L2.
What it does
GoFlightLabs Flight Delay is an MPP (Micropayment Protocol) endpoint that returns flight delay information on a per-call payment basis. It settles via the Tempo method on chain ID 4217 (Tempo L2), charging 5,000 base units of pathUSD (approximately $0.005) per request. The endpoint is live and responds with a valid 402 Payment Required challenge.
This endpoint is part of the broader GoFlightLabs suite, which advertises real-time flight tracking, prices, schedules, and airline data. However, no documentation, OpenAPI schema, or usage examples are available from the provider's MPP gateway — the root domain and all common doc paths return 404. As a result, the exact query parameters (e.g., flight number, airline IATA code, date) and response schema are unknown and must be discovered through experimentation or external GoFlightLabs documentation.
Payment is handled automatically by MPP-compatible agents: the endpoint issues a WWW-Authenticate challenge with intent "charge", and the agent settles the micropayment before receiving the response payload. The fee payer flag is set to true, meaning the provider covers transaction fees on-chain.
Capabilities
Use cases
- —Querying delay status for a specific flight before or during travel
- —Building travel assistant agents that proactively alert users about flight delays
- —Integrating flight delay data into booking or itinerary management workflows
- —Powering dashboards that monitor airline on-time performance
Fit
Best for
- —AI agents needing on-demand flight delay lookups with micropayments
- —Travel chatbots that need real-time delay information
- —Developers building pay-per-use aviation data integrations
Not for
- —Bulk historical flight delay analytics (per-call pricing adds up quickly)
- —Use cases requiring detailed API documentation upfront — docs are currently unavailable
Quick start
curl -i https://goflightlabs.mpp.tempo.xyz/flight-delay
# Returns 402 with WWW-Authenticate: Payment header.
# An MPP-compatible agent settles ~$0.005 in pathUSD on Tempo L2,
# then re-sends the request with a Payment header to receive delay data.Endpoint
Quality
The endpoint is live and returns a valid MPP 402 challenge, confirming it exists and accepts payments. However, there is zero documentation, no OpenAPI schema, no example requests or responses, and all doc/root paths return 404. The request parameters and response format are entirely unknown, making this effectively a stub listing.
Warnings
- —No documentation available — all doc paths on the MPP gateway return 404.
- —Request parameters (flight number, date, airline code, etc.) are unknown; callers must guess or consult external GoFlightLabs docs.
- —Response schema is completely unknown — no examples or OpenAPI spec provided.
- —Currency address 0x20c0...8b50 on chain 4217 is assumed to be pathUSD (6 decimals) based on Tempo conventions, but this is not explicitly confirmed.
Citations
- —Endpoint is live and returns a 402 MPP challenge with method=tempo, intent=charge, amount=5000https://goflightlabs.mpp.tempo.xyz/flight-delay
- —Part of GoFlightLabs suite offering real-time flight tracking, prices, schedules, and airline datahttps://goflightlabs.mpp.tempo.xyz/flight-delay