Search places by text query via Google Maps, paid per-call with pathUSD on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint proxies the Google Maps Places Text Search API through Tempo's payment layer. It accepts a text query describing a place (e.g., "pizza near Times Square") and returns matching place results in JSON format, mirroring the Google Maps Places API response structure.
The endpoint is live and uses the MPP "charge" intent, meaning each request is a one-shot paid call settled in pathUSD on the Tempo L2 network (chain ID 4217). The per-call price is 32,000 base units. Assuming pathUSD uses 6 decimals (consistent with other USD stablecoins), this translates to approximately $0.032 per request. The provider covers gas fees (feePayer: true), so callers only pay the stated amount.
No OpenAPI schema or dedicated documentation was found on the provider's domain. The endpoint path (`/maps/place/textsearch/json`) closely follows the Google Maps Places Text Search endpoint convention, so callers should pass a `query` parameter (and optionally `location`, `radius`, `type`, `language`, etc.) as query-string parameters on a GET request. Responses are expected to follow the standard Google Maps Text Search JSON structure with `results` and `status` fields.
Capabilities
Use cases
- —AI agents searching for businesses or points of interest by name or description
- —Automated itinerary builders that need place details from a text query
- —Chatbots answering user questions about nearby restaurants, hotels, or services
- —Data pipelines enriching addresses with place metadata
Fit
Best for
- —Agents needing pay-per-call Google Maps place search without managing API keys
- —Programmatic place lookups settled via crypto micropayments
- —Low-volume or sporadic place search where a subscription is unnecessary
Not for
- —High-volume batch geocoding where a direct Google Maps API key would be cheaper
- —Use cases requiring directions, routing, or map tile rendering (different endpoints needed)
- —Applications that cannot transact on Tempo L2 or handle MPP payment challenges
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/place/textsearch/json?query=pizza+near+Times+Square"Example
Response
{
"status": "OK",
"results": [
{
"name": "Joe's Pizza",
"types": [
"restaurant",
"food"
],
"rating": 4.5,
"geometry": {
"location": {
"lat": 40.758,
"lng": -73.9855
}
},
"place_id": "ChIJexample123",
"formatted_address": "1535 Broadway, New York, NY 10036"
}
]
}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 example responses were found on the provider's domain. The response format and query parameters are inferred from the Google Maps Places Text Search API convention, not directly documented by the provider.
Warnings
- —No documentation or OpenAPI schema found on the provider domain — all crawled pages returned 404.
- —Response format and query parameters are inferred from Google Maps API conventions, not confirmed by the provider.
- —The currency address (0x20c000000000000000000000b9537d11c60e8b50) is assumed to be pathUSD with 6 decimals; if decimals differ, the actual price would change.
Citations
- —Endpoint returns HTTP 402 with MPP challenge, confirming it is livehttps://googlemaps.mpp.tempo.xyz/maps/place/textsearch/json
- —Payment method is 'tempo' with intent 'charge' on chain ID 4217, amount 32000 base unitshttps://googlemaps.mpp.tempo.xyz/maps/place/textsearch/json
- —Endpoint is described as part of Google Maps Platform — geocoding, directions, places, routes, tiles, weather, air quality, and morehttps://googlemaps.mpp.tempo.xyz/maps/place/textsearch/json