Pay-per-call Google Maps Place Autocomplete via MPP on Tempo L2
What it does
This endpoint proxies the Google Maps Place Autocomplete API through the Micropayment Protocol (MPP), allowing AI agents and applications to obtain place autocomplete suggestions by paying per request with crypto on the Tempo L2 chain (chainId 4217). The upstream Google Maps API returns predicted place results given a partial text query, useful for building location search UIs, geocoding workflows, and address validation pipelines.
The endpoint is live and responds with a standard MPP 402 challenge. Settlement uses the "tempo" method with a one-shot "charge" intent, meaning each request is paid individually. The price is 2,830 base units of the token at contract address 0x20c0…8b50 on chain 4217. Assuming this is a 6-decimal stablecoin (likely pathUSD on Tempo), the per-call cost is approximately $0.00283. The fee payer flag is set to true, so the gateway covers gas fees on behalf of the caller.
Because the provider's origin returns 404 on all documentation and landing pages, no OpenAPI schema, usage examples, or detailed parameter documentation is available from the proxy itself. Callers should refer to the upstream Google Maps Place Autocomplete JSON API documentation for query parameters (e.g., `input`, `types`, `language`, `location`, `radius`) and response structure. The endpoint path (`/maps/place/autocomplete/json`) mirrors the standard Google Maps API path.
Capabilities
Use cases
- —AI agents that need to resolve partial place names or addresses into structured place predictions
- —Building location-aware chatbots that suggest places as users type
- —Automated address validation and normalization pipelines
- —Travel planning agents that search for destinations by partial name
- —Geocoding workflows that need candidate place matches before selecting a final result
Fit
Best for
- —AI agents needing pay-per-call place autocomplete without managing Google API keys
- —Crypto-native applications that want to pay for geo services on Tempo L2
- —Lightweight integrations that only need occasional place lookups
Not for
- —High-volume production apps where a direct Google Maps API key would be cheaper
- —Use cases requiring full Places Details, Directions, or other Maps endpoints not exposed here
- —Applications that cannot settle payments on Tempo L2
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/place/autocomplete/json?input=coffee+near+Times+Square"Example
Response
{
"status": "OK",
"predictions": [
{
"place_id": "ChIJhRoB-5lZwokRsOxoGpbfHQQ",
"description": "Times Square Coffee, New York, NY, USA",
"structured_formatting": {
"main_text": "Times Square Coffee",
"secondary_text": "New York, NY, USA"
}
}
]
}Endpoint
Quality
The endpoint is confirmed live via a valid MPP 402 challenge with clear pricing and settlement details. However, no documentation, OpenAPI schema, or usage examples are available from the provider. Response structure and parameters are inferred from the upstream Google Maps API.
Warnings
- —No documentation pages found on the provider origin (all return 404)
- —No OpenAPI or schema definition available
- —Currency token at 0x20c0…8b50 on chain 4217 is assumed to be a 6-decimal stablecoin but is not explicitly identified — actual per-call cost may differ
- —Response example is inferred from upstream Google Maps API, not from actual endpoint output
Citations
- —Endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=2830 on chainId 4217https://googlemaps.mpp.tempo.xyz/maps/place/autocomplete/json
- —The endpoint path mirrors the Google Maps Place Autocomplete JSON APIhttps://googlemaps.mpp.tempo.xyz/maps/place/autocomplete/json