MPPtempoquality 0.35

Get Google Maps place details via pay-per-call MPP on Tempo L2.

Price
$0.017 / call
Protocol
mpp
Verified
no

What it does

This endpoint exposes Google Maps Place Details functionality through the Micropayment Protocol (MPP), settled on the Tempo L2 chain (chainId 4217) using pathUSD. Each call is a one-shot charge (intent="charge") costing 17,000 base units of pathUSD — which, assuming 6 decimals for pathUSD, equals $0.017 per request.

The endpoint mirrors the Google Maps Places API "Place Details" method, returning detailed information about a specific place given a place ID. Typical response data from the underlying Google API includes the place's name, address, phone number, website, opening hours, reviews, photos, and geographic coordinates. The endpoint is accessed via GET at `/maps/place/details/json`, following the familiar Google Maps query-parameter convention (e.g., `place_id` parameter).

The MPP proxy is hosted at `googlemaps.mpp.tempo.xyz` and is part of a broader Google Maps suite offered through Tempo that also covers geocoding, directions, routes, tiles, weather, and air quality. No OpenAPI schema or documentation pages were found on the proxy origin; the endpoint structure is inferred from the Google Maps Platform conventions and the MPP challenge metadata. Callers must include a valid MPP payment header to receive the actual place details response.

Capabilities

place-detailsgoogle-maps-proxympp-paymenttempo-l2-settlementper-call-billinggeocoding-suite

Use cases

  • Retrieve full details (address, hours, reviews, photos) for a known Google Maps place ID
  • Enrich location data in an agent pipeline without needing a direct Google API key
  • Power chatbot responses about businesses, restaurants, or landmarks with live place data
  • Validate and augment address information in automated workflows

Fit

Best for

  • AI agents needing on-demand place detail lookups with crypto micropayments
  • Developers who want Google Maps data without managing API keys or billing accounts
  • Automated pipelines that need structured venue/business information per request

Not for

  • High-volume batch geocoding where per-call costs add up quickly
  • Use cases requiring real-time directions, routing, or map tile rendering (separate endpoints exist)
  • Users who already have a Google Maps Platform API key and prefer direct access

Quick start

curl -X GET \
  'https://googlemaps.mpp.tempo.xyz/maps/place/details/json?place_id=ChIJN1t_tDeuEmsRUsoyG83frY4' \
  -H 'Authorization: Payment <MPP_PAYMENT_TOKEN>'

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.35/ 1.00

The MPP challenge is live and confirms pricing and settlement details, but no documentation, OpenAPI schema, or example responses were found on the proxy origin. Endpoint behavior and parameters are inferred from Google Maps Platform conventions rather than directly documented.

Warnings

  • No documentation or OpenAPI schema found at the proxy origin — all 5 crawled pages returned 404.
  • Request/response schema is inferred from Google Maps Platform conventions; actual proxy behavior may differ.
  • Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals; if decimals differ, the stated price of $0.017 would be incorrect.
  • No explicit rate limits, terms of service, or usage policies are published.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:01:27Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

Get Google Maps place details via pay-per-call MPP on Tempo L2. — Clawmart · Clawmart