Pay-per-call access to Google Maps Solar API data layers via MPP on Tempo L2.
What it does
This endpoint provides pay-per-call access to the Google Maps Solar API's "dataLayers:get" resource through the Micro-Payment Protocol (MPP), settled on the Tempo L2 chain (chainId 4217). Each call returns solar data layers — typically raster imagery and metadata describing solar potential, building footprints, shade maps, and irradiance data for a given geographic location.
The endpoint is live and returns a standard MPP 402 challenge with intent "charge", meaning each request is a one-shot payment. The price is 75,000 base units of the token at address 0x20c0…8b50 on chain 4217. Assuming this is a 6-decimal stablecoin (e.g., pathUSD on Tempo), the per-call cost is approximately $0.075 (7.5 cents). The fee payer flag is set to true, so the gateway covers gas fees. The payment recipient is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fe.
No OpenAPI schema, documentation pages, or usage examples were found on the gateway itself — all auxiliary routes (docs, api, pricing, README) return 404. The endpoint path mirrors the Google Maps Solar API v1 dataLayers:get method, so callers should consult the upstream Google Solar API documentation for query parameters (latitude, longitude, radius, data layer types, etc.) and response format. Because the crawl yielded no gateway-specific docs, the exact parameter pass-through behavior and response wrapping are inferred rather than confirmed.
Capabilities
Use cases
- —Retrieve solar irradiance and shade data for a specific latitude/longitude to evaluate rooftop solar potential
- —Integrate solar data layers into energy planning or real-estate analysis tools
- —Build agent workflows that assess solar viability for addresses on-the-fly
- —Overlay solar raster imagery onto mapping applications
Fit
Best for
- —AI agents needing programmatic, pay-per-call solar data without managing Google API keys
- —Solar energy feasibility analysis for specific geographic coordinates
- —Automated real-estate or property-tech workflows requiring solar potential data
Not for
- —Bulk batch processing of thousands of locations (per-call pricing adds up)
- —Use cases requiring non-solar Google Maps features like directions, geocoding, or places
Quick start
curl -X GET \
'https://googlemaps.mpp.tempo.xyz/solar/v1/dataLayers:get?location.latitude=37.4219999&location.longitude=-122.0840575&radiusMeters=100' \
-H 'Authorization: Payment <tempo-payment-token>'Endpoint
Quality
The endpoint is live and returns a valid MPP 402 challenge, confirming pricing and settlement details. However, no documentation, OpenAPI schema, or example responses were found on the gateway. Endpoint behavior is inferred entirely from the URL path and upstream Google Solar API conventions.
Warnings
- —No documentation or OpenAPI schema available on the gateway — all doc routes return 404.
- —Currency token address 0x20c0…8b50 on chain 4217 is not independently verified; the $0.075 price assumes 6-decimal stablecoin.
- —Exact query parameter pass-through and response format are inferred from upstream Google Solar API, not confirmed by the gateway.
Citations
- —The endpoint returns a live MPP 402 challenge with intent 'charge', method 'tempo', and amount 75000 base units.https://googlemaps.mpp.tempo.xyz/solar/v1/dataLayers:get
- —Google Solar API dataLayers:get returns solar resource data including irradiance, shade, and building insights.https://developers.google.com/maps/documentation/solar/data-layers