Pay-per-call text search for Google Maps places via MPP on Tempo L2.
What it does
This endpoint wraps Google Maps Platform's Text Search (New) API behind the Micro-Payment Protocol (MPP) on Tempo L2, allowing AI agents and applications to search for places by free-text query (e.g. "pizza near Times Square") and receive structured place results — all settled with per-request crypto payments rather than requiring a Google API key.
The endpoint path `/places/v1/places:searchText` mirrors the Google Maps Places API (New) text search method. It is hosted at googlemaps.mpp.tempo.xyz, which is part of a broader Google Maps MPP gateway offering geocoding, directions, routes, tiles, weather, air quality, and more. Payment is expected to settle via the Tempo L2 network using pathUSD or another supported stablecoin.
Important caveat: during probing, the endpoint returned 404 on both HEAD and GET requests, and no 402 MPP payment challenge was captured. The Text Search endpoint on Google's own API requires POST with a JSON body, so the 404 on GET/HEAD may simply reflect method routing rather than a dead endpoint. However, without a confirmed 402 challenge, pricing details, or any documentation from the provider, the listing cannot be fully verified as live. Treat this listing as provisional.
Capabilities
Use cases
- —Searching for businesses or points of interest by natural-language query
- —Building location-aware AI agents that need place data without managing Google API keys
- —Pay-per-call place lookups for low-volume or bursty workloads
- —Integrating structured place results (name, address, coordinates) into agent workflows
Fit
Best for
- —AI agents needing on-demand place search without API key management
- —Developers who prefer crypto micro-payments over Google billing accounts
- —Low-volume or sporadic place search queries
Not for
- —High-volume production workloads where a direct Google Maps API key is more cost-effective
- —Use cases requiring guaranteed SLA — endpoint liveness is currently unconfirmed
- —Applications needing full Places API features beyond text search (photos, reviews, etc.) unless other endpoints on this gateway are also available
Quick start
curl -X POST https://googlemaps.mpp.tempo.xyz/places/v1/places:searchText \
-H "Content-Type: application/json" \
-d '{"textQuery": "pizza near Times Square"}'Example
Request
{
"textQuery": "pizza near Times Square",
"languageCode": "en"
}Endpoint
Quality
No 402 MPP challenge was captured, no documentation or pricing is available, and all crawled pages returned 404. The endpoint path is recognizable as a Google Maps Text Search proxy, but nothing could be verified live. This is effectively a stub listing.
Warnings
- —Endpoint returned 404 on HEAD and GET — no MPP 402 challenge captured. It may require POST, but this is unconfirmed.
- —No documentation, pricing, or schema available from the provider.
- —Root domain and all common doc paths return 404.
- —Listing is inferred from the URL path and existing Bazaar metadata; treat as provisional.
Citations
- —The endpoint path mirrors Google Maps Places API (New) Text Search methodhttps://developers.google.com/maps/documentation/places/web-service/text-search
- —Part of a broader Google Maps MPP gateway offering geocoding, directions, places, routes, tiles, weather, air quality, and morehttps://googlemaps.mpp.tempo.xyz