Retrieve Google Maps place photos via per-call micropayment on Tempo L2.
What it does
This MPP (Micropayment Protocol) endpoint proxies the Google Maps Places API photo retrieval service. Given a place ID and a photo ID, it returns the corresponding photo media. The endpoint is hosted at googlemaps.mpp.tempo.xyz and settles payments on the Tempo L2 chain (chainId 4217) using pathUSD. Each call costs 7,000 base units of pathUSD (pathUSD uses 6 decimals), which works out to $0.007 per request. The provider covers gas fees (feePayer: true), so callers only pay the listed price.
The URL pattern follows the Google Maps Places API v1 convention: `/places/v1/places/:id/photos/:photoId/media`, where `:id` is the Google Maps place identifier and `:photoId` is the specific photo resource name. The endpoint responds to GET requests and returns photo media content. This is part of a broader Google Maps MPP gateway that also exposes geocoding, directions, routes, tiles, weather, air quality, and other Google Maps Platform capabilities.
Because the crawl yielded no documentation pages, OpenAPI schema, or usage examples, the exact query parameters (e.g., maxWidthPx, maxHeightPx, skipHttpRedirect) and response content-type details are inferred from the upstream Google Maps Places Photo API. Callers familiar with the Google Maps Places API (New) should find the interface familiar, but specifics should be verified against the provider or Google's own documentation.
Capabilities
Use cases
- —Fetching photos of businesses or landmarks by place and photo ID for display in apps
- —Enriching location-based search results with visual imagery
- —Building travel or real-estate tools that show venue photos on demand
- —Agents that need visual context for a Google Maps place without managing API keys directly
Fit
Best for
- —AI agents needing pay-per-call access to Google Maps place photos without API key management
- —Applications that want crypto-settled, metered access to Google Maps imagery
- —Developers prototyping location-aware apps who prefer micropayments over subscription billing
Not for
- —Bulk downloading large volumes of place photos (per-call cost adds up and rate limits are unknown)
- —Use cases requiring photo metadata or attribution info (this endpoint returns media only)
- —Users who already have a Google Maps API key and prefer direct access
Quick start
curl -X GET \
'https://googlemaps.mpp.tempo.xyz/places/v1/places/ChIJN1t_tDeuEmsRUsoyG83frY4/photos/AUy-VnEF3Xv/media?maxWidthPx=400' \
-H 'Authorization: Payment <tempo-payment-token>'Endpoint
Quality
The endpoint is live and returns a valid MPP 402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no examples, and no crawlable content beyond the challenge itself. Most interface details are inferred from the upstream Google Maps API.
Warnings
- —No documentation or OpenAPI schema available from the provider — all docs pages return 404.
- —Exact supported query parameters and response format are inferred from the upstream Google Maps Places Photo API and have not been verified.
- —Currency address 0x20c0…8b50 is assumed to be pathUSD with 6 decimals based on Tempo L2 conventions; if the token differs, the price calculation would change.
Citations
- —The endpoint returns a 402 MPP challenge with method=tempo, intent=charge, amount=7000, chainId=4217, and feePayer=true.https://googlemaps.mpp.tempo.xyz/places/v1/places/:id/photos/:photoId/media
- —Part of a broader Google Maps gateway offering geocoding, directions, places, routes, tiles, weather, air quality, and more.https://googlemaps.mpp.tempo.xyz