Pay-per-call Google Flights search via SerpApi, settled on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint wraps SerpApi's Google Flights search capability behind a pay-per-call paywall settled on Tempo L2 using pathUSD. Each request costs 15,000 base units of pathUSD (pathUSD uses 6 decimals, so this equals $0.015 per call). The endpoint is live and returns a standard MPP 402 challenge with intent "charge", meaning each call is a one-shot payment.
Google Flights search typically returns real-time flight prices, schedules, airlines, layover details, and booking options for given origin/destination pairs and dates. However, the specific query parameters accepted by this endpoint are not documented — no OpenAPI schema, docs page, or README is available at the provider's origin. Based on SerpApi's public API conventions, the endpoint likely accepts query parameters such as `departure_id`, `arrival_id`, `outbound_date`, `return_date`, `type` (round-trip vs one-way), and similar fields, but this cannot be confirmed from the crawled material alone.
The endpoint is hosted at serpapi.mpp.tempo.xyz and uses the Tempo payment method on chain ID 4217. The fee payer flag is set to true, meaning the provider covers transaction fees. The payment recipient address is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fe. The challenge expires far in the future (April 2026), suggesting a long-lived payment configuration.
Capabilities
Use cases
- —AI agents searching for real-time flight prices and schedules on behalf of users
- —Travel planning applications that need programmatic access to Google Flights data
- —Price comparison tools aggregating flight costs across routes and dates
- —Automated travel booking assistants that query available flights before purchasing
Fit
Best for
- —Agents needing on-demand Google Flights data without a SerpApi subscription
- —Low-volume or sporadic flight search queries at $0.015 per call
- —Crypto-native applications that can settle payments on Tempo L2
Not for
- —High-volume flight search workloads where a bulk SerpApi subscription would be cheaper
- —Applications that cannot interact with the MPP/Tempo payment protocol
Quick start
# 1. Obtain a Tempo L2 wallet with pathUSD
# 2. GET the endpoint to receive the 402 challenge
curl https://serpapi.mpp.tempo.xyz/search?departure_id=LAX&arrival_id=JFK&outbound_date=2025-07-01
# 3. Sign and attach a Tempo payment header per MPP spec, then re-send the requestEndpoint
Quality
The endpoint is live (valid 402 MPP challenge captured), and pricing is clear ($0.015/call in pathUSD on Tempo L2). However, there is no documentation, no OpenAPI schema, no example requests or responses, and all crawled pages return 404. Query parameters and response format are entirely inferred from SerpApi conventions.
Warnings
- —No documentation available — all crawled pages (docs, api, pricing, README) return 404.
- —No OpenAPI or schema definition found; request parameters and response structure are unknown.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 conventions; if incorrect, the $0.015 price may be wrong.
- —Root origin returns 404, suggesting the provider has no landing page or public docs.
Citations
- —Endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=15000https://serpapi.mpp.tempo.xyz/search
- —Chain ID is 4217 (Tempo L2) with feePayer=truehttps://serpapi.mpp.tempo.xyz/search
- —Payment recipient is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fehttps://serpapi.mpp.tempo.xyz/search
- —Challenge expires 2026-04-19T16:58:35.384Zhttps://serpapi.mpp.tempo.xyz/search