Pay-per-call nearby place search via Google Maps, settled on Tempo L2 with pathUSD.
What it does
This MPP (Micropayment Protocol) endpoint proxies Google Maps Platform's Nearby Search API, allowing AI agents and applications to discover places near a given location by paying per request with no API key or subscription required. Each call is settled on Tempo L2 (chain ID 4217) using pathUSD at a cost of $0.032 per request (32,000 base units at 6 decimals). The payment intent is "charge", meaning each request is a one-shot micropayment.
The endpoint mirrors the Google Maps Places Nearby Search JSON interface at the path `/maps/place/nearbysearch/json`. Callers supply standard Google Maps query parameters such as `location` (lat,lng), `radius` (meters), and optionally `type` or `keyword` to filter results. The response is expected to follow the standard Google Maps Nearby Search JSON format, returning an array of place results with fields like name, vicinity, geometry, place_id, types, and rating.
No dedicated documentation, OpenAPI schema, or examples are hosted on the provider's origin — all crawled paths return 404. The endpoint itself is live and returns a well-formed 402 MPP challenge. Because this is a proxy of a well-known Google API, callers familiar with the Google Maps Nearby Search API should be able to use it directly, but the lack of provider-hosted docs means exact parameter support and any deviations from the upstream API are unconfirmed.
Capabilities
Use cases
- —Finding restaurants, shops, or services near a given latitude/longitude
- —Agent-driven local business discovery without managing Google API keys
- —Building location-aware recommendation features with pay-per-call pricing
- —Enriching travel or logistics workflows with nearby point-of-interest data
Fit
Best for
- —AI agents needing on-demand nearby place lookups without API key management
- —Low-volume or bursty geo queries where per-call pricing beats a subscription
- —Crypto-native applications that can settle payments on Tempo L2
Not for
- —High-volume batch geocoding or place searches where a direct Google Maps subscription is cheaper
- —Use cases requiring guaranteed SLA, uptime commitments, or vendor support
- —Applications that cannot transact in pathUSD on Tempo L2
Quick start
curl -H "Authorization: Payment <tempo-payment-token>" \
"https://googlemaps.mpp.tempo.xyz/maps/place/nearbysearch/json?location=37.7749,-122.4194&radius=1500&type=restaurant"Example
Response
{
"status": "OK",
"results": [
{
"name": "Example Restaurant",
"types": [
"restaurant",
"food",
"establishment"
],
"rating": 4.3,
"geometry": {
"location": {
"lat": 37.7749,
"lng": -122.4194
}
},
"place_id": "ChIJexampleId",
"vicinity": "123 Main St, San Francisco"
}
]
}Endpoint
Quality
The endpoint is live with a valid 402 MPP challenge and clear pricing, but there is no hosted documentation, no OpenAPI schema, and no examples from the provider. Capability details are inferred from the well-known Google Maps Nearby Search API path and the existing Bazaar description.
Warnings
- —No provider-hosted documentation — all doc paths return 404
- —No OpenAPI or JSON schema available; parameter support is inferred from the Google Maps API convention
- —Currency contract address could not be independently verified as pathUSD; 6-decimal assumption is based on standard stablecoin conventions
- —Exact parity with upstream Google Maps Nearby Search API is unconfirmed
Citations
- —Endpoint returns HTTP 402 with a well-formed MPP challenge, confirming it is livehttps://googlemaps.mpp.tempo.xyz/maps/place/nearbysearch/json
- —Payment amount is 32000 base units settled via Tempo method on chain ID 4217https://googlemaps.mpp.tempo.xyz/maps/place/nearbysearch/json
- —Part of Google Maps Platform suite including geocoding, directions, places, routes, tiles, weather, air qualityhttps://googlemaps.mpp.tempo.xyz