Get elevation data for geographic locations via Google Maps, paid per-call on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint proxies the Google Maps Elevation API through Tempo's payment layer at googlemaps.mpp.tempo.xyz. It returns elevation data for one or more geographic coordinates, wrapping the standard Google Maps Elevation JSON response behind a per-request micropayment wall.
The endpoint is live and responds with a 402 Payment Required challenge using the Tempo settlement method on chain ID 4217. Each request costs 5,000 base units of the configured currency (likely pathUSD with 6 decimals, which would be $0.005 per call). The fee payer flag is set to true, meaning the proxy covers gas fees for the on-chain settlement. Payment intent is "charge", indicating a one-shot payment per API call.
The underlying Google Maps Elevation API accepts latitude/longitude coordinates and returns elevation values in meters along with resolution data. Typical query parameters include `locations` (pipe-delimited lat/lng pairs or an encoded polyline) and optionally `path` with `samples` for elevation along a path. No OpenAPI schema or dedicated documentation is available on the proxy itself; users should refer to the official Google Maps Elevation API documentation for request/response formats.
Capabilities
Use cases
- —Retrieving elevation for GPS coordinates in hiking or outdoor navigation apps
- —Adding terrain height data to geographic datasets for analysis
- —Computing elevation profiles along routes for cycling or running applications
- —Enriching location-based services with altitude information
- —Assessing flood risk or drainage by querying elevation at specific points
Fit
Best for
- —Agents needing per-call elevation data without managing Google API keys
- —Crypto-native applications that can pay with pathUSD on Tempo L2
- —Lightweight elevation queries for small batches of coordinates
Not for
- —High-volume bulk elevation queries where a direct Google Maps API key would be cheaper
- —Applications requiring sub-meter elevation precision (this returns standard Google Maps resolution)
- —Users who cannot transact on the Tempo L2 chain
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/elevation/json?locations=39.7391536,-104.9847034"Example
Response
{
"status": "OK",
"results": [
{
"location": {
"lat": 39.7391536,
"lng": -104.9847034
},
"elevation": 1608.637939453125,
"resolution": 4.771975994110107
}
]
}Endpoint
Quality
The endpoint is live with a valid 402 MPP challenge, confirming it proxies Google Maps Elevation. However, no documentation, OpenAPI schema, or examples are available from the proxy itself. Response format and pricing details are inferred from the challenge and knowledge of the upstream Google Maps API.
Warnings
- —No documentation or OpenAPI schema available on the proxy — all crawled pages return 404.
- —Currency address 0x20c0...8b50 on chain 4217 is not independently verified; price of $0.005 assumes pathUSD with 6 decimals.
- —Response format is inferred from the standard Google Maps Elevation API and not confirmed by the proxy.
Citations
- —The endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=5000 on chainId 4217.https://googlemaps.mpp.tempo.xyz/maps/elevation/json
- —Google Maps Elevation API returns elevation in meters with resolution data for given lat/lng coordinates.https://developers.google.com/maps/documentation/elevation/overview