Find a place from a text query via Google Maps, paid per-call with pathUSD on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint wraps the Google Maps "Find Place from Text" API behind a pay-per-call Tempo L2 payment wall. It accepts a text query (such as a business name, address, or point of interest) and returns matching place results from Google Maps, including place IDs, addresses, and other details.
The endpoint is live and responds with a standard MPP 402 challenge. Payment settles in pathUSD on Tempo (chain ID 4217) at a cost of 17,000 base units per request. Assuming pathUSD uses 6 decimals (consistent with other USD stablecoins), this equates to approximately $0.017 per call. The provider covers gas fees (feePayer: true), so callers only need to sign the payment — no separate gas token is required.
The URL structure (`/maps/place/findplacefromtext/json`) mirrors the Google Maps Places API path, suggesting the upstream query parameters are the same as the standard Google Maps Find Place from Text endpoint (e.g., `input`, `inputtype`, `fields`). However, no OpenAPI schema, documentation pages, or examples were found on the provider's domain — all auxiliary routes return 404. Callers should refer to the official Google Maps Find Place from Text documentation for parameter details and adapt accordingly.
Capabilities
Use cases
- —Resolve a business name or address string to a Google Maps place ID and structured address
- —Enrich user-submitted location text with coordinates and place metadata
- —Power location autocomplete or validation in agent workflows
- —Look up points of interest programmatically without managing a Google API key
Fit
Best for
- —AI agents that need on-demand place lookups without provisioning Google API credentials
- —Micropayment-native workflows that settle on Tempo L2
- —Low-volume or sporadic geocoding tasks where per-call pricing is more economical than a subscription
Not for
- —High-volume batch geocoding where a direct Google Maps API key would be cheaper
- —Use cases requiring directions, routing, or other Maps APIs beyond place search
Quick start
curl -H "Authorization: Payment <signed-tempo-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/place/findplacefromtext/json?input=Museum+of+Modern+Art&inputtype=textquery&fields=place_id,formatted_address,name,geometry"Endpoint
Quality
The endpoint is live with a valid MPP 402 challenge confirming pricing and settlement details. However, there is no OpenAPI schema, no documentation, no examples, and all auxiliary pages return 404. Parameter semantics are inferred from the URL path matching Google's own API structure, not from provider-supplied docs.
Warnings
- —No documentation, OpenAPI schema, or examples found on the provider domain — all pages return 404.
- —Query parameters are inferred from the Google Maps Find Place from Text API; the provider has not confirmed supported parameters or response format.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if decimals differ, the actual price would change.
Citations
- —Endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=17000, chainId=4217, feePayer=truehttps://googlemaps.mpp.tempo.xyz/maps/place/findplacefromtext/json
- —Challenge expires 2026-04-19T17:12:55.688Z and recipient is 0xca4e835F803cB0b7C428222B3A3B98518d4779Fehttps://googlemaps.mpp.tempo.xyz/maps/place/findplacefromtext/json