Hourly weather forecast via Google Maps Platform, paid per-call on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint provides hourly weather forecasts sourced from the Google Maps Platform. It is hosted at googlemaps.mpp.tempo.xyz and uses the Tempo settlement method (pathUSD on Tempo L2, chain ID 4217) with a per-call charge of 150 base units. Assuming the currency uses 6 decimals (consistent with pathUSD), each request costs $0.000150 — a fraction of a cent per call. The endpoint path follows the Google Maps Weather API convention: `/weather/v1/forecast/hours:lookup`.
The endpoint is live and returns a valid 402 Payment Required challenge when probed, confirming it is operational and awaiting payment authorization before serving data. The fee-payer flag is set to true, meaning the service provider covers gas fees for the on-chain settlement. No OpenAPI schema, documentation pages, or usage examples were found on the provider's domain; all auxiliary routes (docs, api, pricing, README) return 404. As a result, the exact request parameters (e.g., how to specify location coordinates, time range, or units) must be inferred from the upstream Google Maps Weather API documentation.
This endpoint is part of a broader Google Maps proxy suite on Tempo that also exposes geocoding, directions, places, routes, tiles, and air quality endpoints. It is designed for AI agents and automated workflows that need programmatic, pay-per-use access to weather data without managing API keys or billing accounts directly with Google.
Capabilities
Use cases
- —Retrieve hourly weather forecasts for a given location in an automated agent workflow
- —Integrate weather data into route-planning or logistics applications
- —Power weather-aware notifications or dashboards without managing Google API keys
- —Feed weather context into LLM-based travel or outdoor activity planners
Fit
Best for
- —AI agents needing on-demand hourly weather data with micropayment settlement
- —Developers who want Google Maps weather data without a direct Google billing account
- —Automated pipelines requiring pay-per-call weather forecasts at sub-cent cost
Not for
- —Bulk historical weather data retrieval (no batch endpoint documented)
- —Use cases requiring free or ad-supported weather data
- —Applications needing real-time minute-by-minute precipitation nowcasting
Quick start
# Probe the endpoint to receive the 402 payment challenge
curl -i https://googlemaps.mpp.tempo.xyz/weather/v1/forecast/hours:lookup
# After settling payment via Tempo L2, include the payment proof header
# to receive the hourly weather forecast JSON response.Endpoint
Quality
The endpoint is confirmed live via a valid 402 MPP challenge, and pricing details are extractable from the decoded request. However, there is no OpenAPI schema, no documentation, no request/response examples, and all doc routes return 404. Most usage details must be inferred from upstream Google Maps Weather API conventions.
Warnings
- —No documentation or OpenAPI schema found on the provider domain — all auxiliary routes return 404.
- —Request parameters (location, time range, units) are undocumented; must be inferred from upstream Google Maps Weather API docs.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if different, the price calculation would change.
- —No example request or response available.
Citations
- —Endpoint returns HTTP 402 with a valid MPP payment challenge, confirming it is live.https://googlemaps.mpp.tempo.xyz/weather/v1/forecast/hours:lookup
- —Settlement method is Tempo on chain ID 4217 with amount 150 base units and feePayer enabled.https://googlemaps.mpp.tempo.xyz/weather/v1/forecast/hours:lookup
- —Part of a broader Google Maps proxy suite including geocoding, directions, places, routes, tiles, weather, and air quality.https://googlemaps.mpp.tempo.xyz