Pay-per-call Google Maps Place Details (essentials) via MPP on Tempo L2.
What it does
This endpoint provides Google Maps Place Details in an "essentials" tier through the Micropayment Protocol (MPP), settled on the Tempo L2 chain (chainId 4217). Callers send a GET request to `https://googlemaps.mpp.tempo.xyz/places/v1/places/:id`, replacing `:id` with a Google Maps place ID. The endpoint returns a 402 Payment Required challenge; once the caller satisfies the payment (5,000 base units of pathUSD on Tempo, i.e. $0.005 per call assuming 6-decimal pathUSD), the upstream Google Maps Places API response is proxied back.
The endpoint is part of a broader Google Maps MPP gateway that appears to wrap multiple Google Maps Platform services — geocoding, directions, places, routes, tiles, weather, air quality, and more — behind per-call crypto micropayments. Each call is a one-shot charge (intent="charge"), and the provider covers gas fees (feePayer: true), so the caller only needs to authorize the pathUSD payment.
No OpenAPI schema, documentation pages, or example responses were found on the provider's origin. The endpoint structure (`/places/v1/places/:id`) mirrors the Google Maps Places API (New) "Get Place" method, so the response is expected to follow that schema — returning fields like displayName, formattedAddress, location, types, and other essentials-tier fields. Because no docs are hosted, callers should refer to the official Google Maps Places API documentation for field definitions and consult the MPP payment flow for authentication.
Capabilities
Use cases
- —Retrieve address, name, and location for a known Google Maps place ID without needing a Google API key
- —Integrate place details into an AI agent workflow with per-call crypto micropayments
- —Build location-aware applications that pay only for the queries they make
Fit
Best for
- —AI agents needing on-demand place details without managing Google API credentials
- —Low-volume or bursty place lookups where per-call pricing is more economical than a subscription
- —Crypto-native applications that prefer on-chain settlement over traditional billing
Not for
- —High-volume batch geocoding where Google's native bulk pricing would be cheaper
- —Use cases requiring full Place Details (not just essentials-tier fields)
- —Applications that cannot transact in pathUSD on Tempo L2
Quick start
curl -i https://googlemaps.mpp.tempo.xyz/places/v1/places/ChIJN1t_tDeuEmsRUsoyG83frY4
# Returns 402 with WWW-Authenticate: Payment header.
# Satisfy the MPP challenge with a signed Tempo L2 pathUSD payment to complete the request.Endpoint
Quality
The endpoint is live and returns a well-formed MPP 402 challenge with clear pricing and settlement details. However, no documentation, OpenAPI schema, or example responses are available from the provider. The response format is inferred from the Google Maps Places API (New) convention, not confirmed by the provider.
Warnings
- —No documentation or OpenAPI schema found on the provider origin (all doc paths return 404).
- —Response schema is inferred from Google Maps Places API conventions and not confirmed.
- —Currency contract address (0x20c0...8b50) assumed to be pathUSD with 6 decimals; if decimals differ, the $0.005 price estimate would be wrong.
- —Root origin returns 404 — no landing page or service description available.
Citations
- —The endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=5000, chainId=4217https://googlemaps.mpp.tempo.xyz/places/v1/places/:id
- —Part of a broader Google Maps gateway covering geocoding, directions, places, routes, tiles, weather, air quality, and morehttps://googlemaps.mpp.tempo.xyz
- —The URL pattern /places/v1/places/:id mirrors the Google Maps Places API (New) Get Place methodhttps://developers.google.com/maps/documentation/places/web-service/place-details