Google Maps Place Autocomplete via MPP micropayment protocol on Tempo
What it does
This endpoint wraps Google Maps Platform's Place Autocomplete API and exposes it through the Micropayment Protocol (MPP) on Tempo's infrastructure. Place Autocomplete returns place predictions (addresses, businesses, points of interest) as a user types, making it useful for search-ahead UIs, address entry forms, and location-based agent workflows.
The endpoint is hosted at googlemaps.mpp.tempo.xyz and follows the Google Maps Places API v1 path convention (`/places/v1/places:autocomplete`). It is expected to settle payments in pathUSD on the Tempo L2 network. However, during probing the endpoint returned HTTP 404 on both HEAD and GET requests, and no 402 MPP payment challenge was captured. The provider's root domain and all documentation paths also return 404, suggesting the endpoint may not yet be deployed, may have been moved, or may only respond to POST requests matching the Google Places Autocomplete contract.
Because no schema, pricing, or documentation was retrievable, all capability details are inferred from the endpoint path and the existing catalog description referencing Google Maps Platform services. Users should verify availability before relying on this endpoint.
Capabilities
Use cases
- —Providing real-time place suggestions as a user types in a search box
- —Validating and completing partial addresses in checkout or registration forms
- —Enabling AI agents to resolve ambiguous location references to structured place data
- —Building location-aware chatbots that suggest nearby businesses or landmarks
Fit
Best for
- —Agents needing pay-per-call place autocomplete without managing Google API keys
- —Developers integrating location search into crypto-native or micropayment workflows
- —Applications requiring address completion with on-chain settlement
Not for
- —High-volume batch geocoding where a direct Google Maps API key is more cost-effective
- —Use cases requiring driving directions, route optimization, or map tile rendering
Quick start
curl -X POST https://googlemaps.mpp.tempo.xyz/places/v1/places:autocomplete \
-H 'Content-Type: application/json' \
-d '{"input": "1600 Amphitheatre"}'Example
Request
{
"input": "1600 Amphitheatre"
}Endpoint
Quality
The endpoint returned 404 on all probe methods and no MPP 402 challenge was captured. All documentation paths return 404. No schema, pricing, or examples are available. Listing details are almost entirely inferred from the URL path and catalog metadata.
Warnings
- —Endpoint returned 404 on HEAD and GET — no MPP 402 challenge captured; it may only accept POST or may not be live
- —All documentation and root paths return 404 — no provider docs available
- —No pricing information available — payment amount and currency are unknown
- —Capabilities are inferred from URL path and catalog description, not from verified API responses
- —The endpoint may require a POST request body matching Google Places Autocomplete v1 format, which was not tested in the probe