Pay-per-call geocoding and reverse-geocoding via Google Maps, settled on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint wraps the Google Maps Geocoding API, allowing AI agents and automated clients to geocode street addresses into latitude/longitude coordinates or reverse-geocode coordinates back into human-readable addresses. Each call is paid individually via the Tempo L2 settlement method using pathUSD (6 decimals), at a cost of $0.005 (0.5 cents) per request. The provider handles the upstream Google Maps API key so callers don't need their own.
The endpoint mirrors the standard Google Maps Geocoding API path (`/maps/geocode/json`) and accepts GET requests with query parameters such as `address` (for forward geocoding) or `latlng` (for reverse geocoding). Responses are expected to follow the familiar Google Geocoding JSON format, including `results` arrays with `formatted_address`, `geometry.location`, `address_components`, and `place_id` fields.
The endpoint is live and returns a valid 402 Payment Required challenge with Tempo settlement details. Chain ID 4217 is used, and the provider covers transaction fees (`feePayer: true`). No OpenAPI schema, documentation pages, or usage examples are published by the provider — all crawled doc/pricing/README paths return 404. The API surface is inferred from the Google Maps Geocoding API conventions and the endpoint path.
Capabilities
Use cases
- —Convert a street address into geographic coordinates for mapping or routing
- —Reverse-geocode GPS coordinates into a formatted street address
- —Enrich contact or business records with standardized address components
- —Validate and normalize user-entered addresses
- —Provide location context to an AI agent without managing a Google Maps API key
Fit
Best for
- —AI agents needing on-demand geocoding without API key management
- —Low-volume or sporadic geocoding where per-call pricing is simpler than a subscription
- —Crypto-native applications that prefer on-chain micropayment settlement
Not for
- —High-volume batch geocoding where bulk pricing would be far cheaper
- —Applications requiring additional Google Maps services (directions, places, etc.) in a single call
- —Users who need guaranteed SLA or official Google Maps support
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA"Example
Response
{
"status": "OK",
"results": [
{
"geometry": {
"location": {
"lat": 37.4224764,
"lng": -122.0842499
}
},
"place_id": "ChIJ2eUgeAK6j4ARbn5u_wAGqWA",
"formatted_address": "1600 Amphitheatre Pkwy, Mountain View, CA 94043, USA",
"address_components": [
{
"types": [
"street_number"
],
"long_name": "1600",
"short_name": "1600"
}
]
}
]
}Endpoint
Quality
The endpoint is live with a valid 402 MPP challenge and clear pricing, but there is no published OpenAPI schema, no documentation, and all auxiliary pages return 404. The API surface and response format are inferred from Google Maps Geocoding conventions rather than directly sourced from the provider.
Warnings
- —No OpenAPI or JSON schema published by the provider
- —All documentation, pricing, and README pages return 404
- —Response format is inferred from Google Maps Geocoding API conventions, not confirmed by provider docs
- —Currency contract address (0x20c0…8b50) assumed to be pathUSD with 6 decimals based on Tempo L2 conventions; if incorrect, the actual price may differ
Citations
- —Endpoint returns HTTP 402 with a valid MPP challenge using Tempo settlement methodhttps://googlemaps.mpp.tempo.xyz/maps/geocode/json
- —Per-call amount is 5000 base units on chain ID 4217 with feePayer truehttps://googlemaps.mpp.tempo.xyz/maps/geocode/json
- —Challenge description states: Geocode an address or reverse-geocode coordinateshttps://googlemaps.mpp.tempo.xyz/maps/geocode/json