Pay-per-call hourly weather history via Google Maps, settled on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint proxies Google Maps Platform's hourly weather history lookup through Tempo's payment layer. Each call is a one-shot charge settled in pathUSD on the Tempo L2 network (chain ID 4217). The endpoint lives at `googlemaps.mpp.tempo.xyz/weather/v1/history/hours:lookup` and returns a standard 402 Payment Required challenge when called without payment credentials, confirming it is live.
The price per request is 150 base units of pathUSD (6 decimals), which equals $0.000150 — a fraction of a cent per call. The provider covers gas fees (feePayer: true), so callers only pay the stated amount. This endpoint is part of a broader Google Maps MPP gateway that also exposes geocoding, directions, places, routes, tiles, and air-quality APIs.
Documentation is sparse: the proxy origin returns 404 on all common doc paths (/docs, /api, /pricing, /README). The underlying API likely mirrors Google's Weather API `hours:lookup` method, which accepts location coordinates and a time range and returns historical hourly weather observations. Without an OpenAPI spec or explicit parameter documentation from the proxy, callers should refer to Google's official Weather API reference for request/response structure and pass the same query parameters or JSON body through this endpoint.
Capabilities
Use cases
- —Retrieve historical hourly weather data for a given location and time range
- —Power analytics dashboards that correlate weather with business metrics
- —Feed weather context into AI agents making location-aware decisions
- —Backfill weather datasets for machine-learning training pipelines
Fit
Best for
- —Agents needing on-demand historical weather without managing API keys
- —Micropayment-based access to Google Maps weather data
- —Developers who want gas-free crypto settlement for per-call billing
Not for
- —Real-time weather forecasting (this is historical data only)
- —High-volume bulk historical weather downloads where a direct Google Maps subscription would be cheaper
- —Users who need detailed API documentation at the proxy layer
Quick start
curl -X GET \
'https://googlemaps.mpp.tempo.xyz/weather/v1/history/hours:lookup?location.latitude=37.7749&location.longitude=-122.4194' \
-H 'Authorization: Payment <tempo-payment-token>'Endpoint
Quality
The endpoint is confirmed live via a valid 402 MPP challenge with clear pricing and settlement details, but there is no OpenAPI spec, no documentation, no example request/response, and all doc paths return 404. Most technical details are inferred from the Google Maps Weather API and the MPP challenge alone.
Warnings
- —No OpenAPI or schema documentation available from the proxy
- —All documentation paths (/docs, /api, /pricing, /README) return 404
- —Request and response formats are inferred from Google's official Weather API and are not confirmed by the proxy provider
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on Tempo conventions; if decimals differ, the stated price would be wrong
Citations
- —Endpoint returns HTTP 402 with MPP challenge confirming it is livehttps://googlemaps.mpp.tempo.xyz/weather/v1/history/hours:lookup
- —Price is 150 base units, settlement via Tempo method on chain ID 4217 with feePayer truehttps://googlemaps.mpp.tempo.xyz/weather/v1/history/hours:lookup
- —Part of a broader Google Maps gateway covering geocoding, directions, places, routes, tiles, weather, air qualityhttps://googlemaps.mpp.tempo.xyz