Pay-per-call nearby place search via Google Maps on Tempo MPP
What it does
This endpoint wraps Google Maps Platform's Nearby Search API and exposes it through the Tempo MPP (Micropayment Protocol) at `https://googlemaps.mpp.tempo.xyz/places/v1/places:searchNearby`. It is intended to let AI agents and applications search for places near a given location (by category, radius, etc.) and pay per request using pathUSD on the Tempo L2 settlement layer.
The endpoint is part of a broader Google Maps MPP gateway that reportedly covers geocoding, directions, places, routes, tiles, weather, air quality, and more. However, during probing the endpoint returned HTTP 404 on both HEAD and GET requests, and no 402 payment challenge was captured. The provider's root domain and all documentation paths also returned 404. This means the endpoint may require a POST method (consistent with the Google Maps `searchNearby` API design) or it may be temporarily unavailable.
Because no payment challenge, schema, pricing, or documentation could be retrieved, nearly all details about this listing are inferred from the endpoint path and the existing catalog description. Users should verify availability before relying on this endpoint in production.
Capabilities
Use cases
- —Finding restaurants, shops, or services near a given latitude/longitude
- —Agent-driven itinerary planning that needs nearby points of interest
- —Location-aware applications that need pay-per-call place data without managing Google API keys
Fit
Best for
- —AI agents needing on-demand nearby place lookups with micropayment billing
- —Developers who want Google Maps place data without a direct Google Cloud account
- —Pay-as-you-go place search without monthly commitments
Not for
- —Bulk geocoding or large-scale place data extraction (likely expensive per-call)
- —Use cases requiring guaranteed uptime — endpoint liveness could not be confirmed
Quick start
curl -X POST https://googlemaps.mpp.tempo.xyz/places/v1/places:searchNearby \
-H "Content-Type: application/json" \
-d '{"includedTypes":["restaurant"],"locationRestriction":{"circle":{"center":{"latitude":37.7749,"longitude":-122.4194},"radius":500}}}'Example
Request
{
"includedTypes": [
"restaurant"
],
"locationRestriction": {
"circle": {
"center": {
"latitude": 37.7749,
"longitude": -122.4194
},
"radius": 500
}
}
}Endpoint
Quality
The endpoint returned 404 on all probe methods and no 402 MPP challenge was captured. All documentation paths returned 404. Listing details are almost entirely inferred from the URL path and catalog metadata; no schema, pricing, or live response data is available.
Warnings
- —Endpoint returned 404 on HEAD and GET — may require POST or may be down
- —No MPP 402 payment challenge was captured; pricing and settlement details are unknown
- —All documentation and root paths return 404; provider site appears non-functional
- —No OpenAPI schema or response examples available
- —Liveness could not be confirmed — endpoint may be inactive or misconfigured
Citations
- —Endpoint is part of a Google Maps MPP gateway covering geocoding, directions, places, routes, tiles, weather, air quality, and morehttps://googlemaps.mpp.tempo.xyz
- —Endpoint returned 404 on HEAD and GET probe attemptshttps://googlemaps.mpp.tempo.xyz/places/v1/places:searchNearby