MPPtempoquality 0.35

Query airports by filters via a pay-per-call flight-data API on Tempo L2.

Price
$0.005 / call
Protocol
mpp
Verified
no

What it does

GoFlightLabs — Airports by Filters is an MPP (Micropayment Protocol) endpoint that returns airport data filtered by caller-specified criteria. It is part of the broader GoFlightLabs suite, which provides real-time flight tracking, pricing, schedules, and airline data. Each call is settled on Tempo L2 (chain ID 4217) using pathUSD at $0.005 per request.

The endpoint is live and responds with a standard MPP 402 payment challenge on GET requests. Payment is handled via the Tempo method with a one-shot "charge" intent, meaning each API call is independently paid for. The fee payer flag is set to true, so the provider covers on-chain transaction fees. No OpenAPI schema or documentation pages were found on the MPP gateway itself, so the exact query parameters and response shape must be inferred from the GoFlightLabs upstream API or discovered experimentally.

Because no docs, schema, or example responses are available from the MPP host, integrators should expect standard airport-filter parameters (e.g., country code, IATA/ICAO codes, city, timezone) and JSON responses containing airport records. Consult the upstream GoFlightLabs documentation for parameter details.

Capabilities

airport-searchairport-filteringflight-datapay-per-callmpp-tempomicropayments

Use cases

  • Filtering airports by country, city, or code for travel applications
  • Building flight-booking tools that need airport metadata on demand
  • Enriching travel-agent AI workflows with structured airport data
  • Powering airport autocomplete or selection widgets

Fit

Best for

  • AI agents needing on-demand airport data without API-key management
  • Low-volume, pay-per-call airport lookups settled in crypto
  • Developers integrating flight data into micropayment-native applications

Not for

  • High-volume bulk airport data downloads (per-call pricing adds up)
  • Use cases requiring full OpenAPI schema validation before integration
  • Users who need fiat-only payment rails (this endpoint uses Tempo/pathUSD)

Quick start

curl -i "https://goflightlabs.mpp.tempo.xyz/airports-by-filters?country=US"
# Returns 402 with WWW-Authenticate: Payment header.
# Submit a Tempo payment proof to unlock the response.

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.35/ 1.00

The endpoint is live (402 MPP challenge confirmed) and pricing is clear ($0.005/call in pathUSD on Tempo L2), but there is no documentation, no OpenAPI schema, no example responses, and all crawled pages return 404. The listing is largely inferred from the challenge metadata and the existing description.

Warnings

  • No documentation or schema found at the MPP gateway — all /docs, /api, /pricing, /README paths return 404.
  • Exact query parameters and response format are unknown; must be inferred from upstream GoFlightLabs docs.
  • Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD (6 decimals) on chain 4217; if decimals differ, the stated price is wrong.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:54:48Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access