MPPtempoquality 0.92

Get partial Google Maps place details by place ID for $0.02 per request via micropayment.

Price
$0.02 / call
Protocol
mpp
Verified
no

What it does

This endpoint retrieves partial details for a specific Google Maps place given its place ID. It is a GET endpoint hosted at `https://stableenrich.dev/api/google-maps/place-details/partial` and is part of the StableEnrich platform, which unifies multiple data sources behind a single pay-per-request interface with no subscriptions or API keys required.

The partial variant returns basic place information including display name, formatted address, location coordinates, place types, business status, Google Maps URI, and optionally ratings, opening hours, and reviews. It excludes the richer atmosphere data (e.g., detailed service flags, parking options) that the full variant ($0.05/request) provides, making it a cost-effective choice when only core place metadata is needed. The endpoint costs $0.02 per request, paid via x402 or MPP (Tempo method on chain 4217 using pathUSD). Photos are excluded by default but can be included by passing an empty `excludeFields` array.

Payment is handled automatically through the MPP or x402 protocol — the endpoint returns HTTP 402 with payment challenge headers when called without payment. The `placeId` query parameter is required. An optional `languageCode` parameter defaults to English. The response schema includes fields like `id`, `displayName`, `formattedAddress`, `location`, `types`, `rating`, `userRatingCount`, `regularOpeningHours`, `reviews`, and more.

Capabilities

place-details-lookupgoogle-maps-apipartial-field-responsemicropayment-authfield-filteringget-by-place-id

Use cases

  • Retrieving basic info (name, address, coordinates) for a known Google Maps place ID
  • Validating or enriching place data obtained from a prior text or nearby search
  • Getting opening hours and ratings for a specific business without paying for full details
  • Building location-aware agent workflows that need lightweight place metadata

Fit

Best for

  • Agents that already have a place ID from a prior search and need basic details cheaply
  • Cost-sensitive lookups where full reviews, atmosphere flags, and contact info aren't needed
  • Programmatic place verification in enrichment pipelines

Not for

  • Discovering places by text query or location (use the text-search or nearby-search endpoints instead)
  • Getting full atmosphere data, detailed service flags, or comprehensive reviews (use the /full variant at $0.05)
  • Bulk geocoding or address resolution without a Google Maps place ID

Quick start

# Fetch partial place details (requires MPP or x402 payment)
curl -I 'https://stableenrich.dev/api/google-maps/place-details/partial?placeId=ChIJN1t_tDeuEmsRUsoyG83frY4&excludeFields=photos'

Example

Response

{
  "id": "ChIJN1t_tDeuEmsRUsoyG83frY4",
  "types": [
    "performing_arts_theater",
    "tourist_attraction",
    "point_of_interest"
  ],
  "rating": 4.7,
  "location": {
    "latitude": -33.8567844,
    "longitude": 151.2152967
  },
  "displayName": {
    "text": "Sydney Opera House",
    "languageCode": "en"
  },
  "primaryType": "performing_arts_theater",
  "googleMapsUri": "https://maps.google.com/?cid=...",
  "businessStatus": "OPERATIONAL",
  "userRatingCount": 48523,
  "formattedAddress": "Bennelong Point, Sydney NSW 2000, Australia"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.92/ 1.00

Full OpenAPI 3.1 schema with request parameters, response schema, and clear pricing is available. The MPP 402 challenge was captured live confirming the endpoint is operational. Docs and guidance are comprehensive. The example response is synthesized from the schema since no live 200 response was captured, which is the only minor gap.

Warnings

  • The example response JSON is inferred from the OpenAPI schema, not captured from a live 200 response.
  • The MPP challenge shows amount=20000 with pathUSD on Tempo (chain 4217); assuming 6 decimals this equals $0.02, consistent with documented pricing. However the currency address in the challenge (0x20c000000000000000000000b9537d11c60e8b50) differs slightly from the OpenAPI x-payment-info currency field — this may reflect chain-specific token addressing.

Citations

Provenance

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

Agent access