Pay-per-call building solar insights via Google Maps Solar API, settled on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint proxies the Google Maps Solar API's `buildingInsights:findClosest` method. Given a geographic location, it returns solar energy potential data for the nearest building — including roof geometry, solar panel layout estimates, annual sunshine hours, and energy production projections. The endpoint is live and uses the Tempo payment method (pathUSD on chain 4217) with a per-call charge intent.
Each request costs 10,000 base units of pathUSD. Assuming pathUSD uses 6 decimals (consistent with other USD stablecoins), this translates to $0.01 per call. The fee payer flag is set to true, meaning the provider covers gas fees for the payment settlement. The challenge expires in April 2026, indicating long-term availability.
The underlying Google Maps Solar API typically accepts query parameters such as `location.latitude` and `location.longitude` to identify the building closest to the given coordinates. The response includes detailed solar potential data: roof segment information, panel counts and configurations, estimated annual energy output in kWh, and financial analysis for solar installation. No OpenAPI schema or documentation pages were found on the proxy origin itself, so consumers should refer to the official Google Maps Solar API documentation for request/response structure.
Capabilities
Use cases
- —Estimating solar panel installation potential for a specific building by coordinates
- —Providing solar energy production forecasts in real-estate or property-tech applications
- —Powering solar cost-benefit calculators with per-building roof and sunshine data
- —Enriching geographic datasets with solar potential metadata for urban planning
Fit
Best for
- —Agents needing per-call solar building data without a Google Cloud billing account
- —Applications that want crypto-settled micropayments for Google Maps Solar queries
- —Prototyping solar energy tools with low per-request cost ($0.01/call)
Not for
- —Bulk batch processing of thousands of buildings (per-call pricing adds up)
- —Use cases requiring full Google Maps Platform features beyond Solar (directions, places, etc.) in a single call
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/solar/v1/buildingInsights:findClosest?location.latitude=37.4219999&location.longitude=-122.0840575"Endpoint
Quality
The endpoint is live with a valid 402 MPP challenge and clear pricing, but no OpenAPI schema, documentation, or example responses are available from the proxy origin. Request/response structure must be inferred from the upstream Google Maps Solar API docs.
Warnings
- —No OpenAPI schema or documentation found on the proxy origin — all 5 crawled pages returned 404.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo L2 conventions; this is not independently verified from the crawl.
- —Request and response formats are inferred from the upstream Google Maps Solar API and not confirmed by the proxy provider.
Citations
- —The endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=10000, chainId=4217https://googlemaps.mpp.tempo.xyz/solar/v1/buildingInsights:findClosest
- —Google Maps Solar API buildingInsights:findClosest returns solar potential data for the nearest buildinghttps://developers.google.com/maps/documentation/solar/building-insights