MPPtempoquality 0.92

Google Maps text search returning basic place details at $0.02/request via micropayment

Price
$0.02 / call
Protocol
mpp
Verified
no

What it does

This endpoint performs a Google Maps text search and returns partial (basic) place details. It is part of StableEnrich, a pay-per-request research API gateway that unifies multiple data sources behind a single interface with micropayment authentication. No API keys or subscriptions are required.

The partial text search endpoint accepts a text query (e.g., "coffee shops in San Francisco") and returns up to 5 results per request with basic place information including place ID, display name, formatted address, location coordinates, place types, business status, Google Maps URI, and accessibility options. It also supports optional filters such as locationBias (circle with center/radius), includedType, openNow, minRating, priceLevels, and language code. Pagination is supported via pageToken (returned as nextPageToken in responses). Photos are excluded by default but can be included by passing an empty excludeFields array.

Priced at $0.02 per request, this is the lower-cost alternative to the full text search endpoint ($0.08) which additionally includes ratings, reviews, contact info, and atmosphere data. Payment is handled via x402 or MPP (Tempo method with pathUSD currency) on Base mainnet, Solana, or Tempo. The endpoint is a POST request and uses the same request body schema as the full variant.

Capabilities

google-maps-text-searchplace-discoverylocation-bias-filteringpaginationfield-filteringmicropayment-authx402mpp-tempo

Use cases

  • Finding businesses or points of interest by text query with basic details
  • Building location-aware agent workflows that need place names and addresses
  • Low-cost place discovery before drilling into full details on specific places
  • Populating maps or lists with basic place data for a given search term
  • Screening places by type, price level, or open-now status before enrichment

Fit

Best for

  • Agents needing cheap, basic place info (name, address, coordinates) from a text query
  • Workflows that filter places before paying for full details on selected results
  • Bulk place discovery where cost matters more than review/contact data
  • Location-based research pipelines that combine with other StableEnrich endpoints

Not for

  • Use cases requiring reviews, ratings, contact info, or atmosphere data (use the /full variant instead)
  • Nearby search by geographic coordinates without a text query (use /nearby-search/partial)
  • Reverse geocoding or address validation

Quick start

POST https://stableenrich.dev/api/google-maps/text-search/partial
Content-Type: application/json

{
  "textQuery": "coffee shops in San Francisco",
  "maxResultCount": 3
}

Example

Request

{
  "textQuery": "coffee shops in San Francisco",
  "locationBias": {
    "circle": {
      "center": {
        "latitude": 37.7749,
        "longitude": -122.4194
      },
      "radius": 5000
    }
  },
  "maxResultCount": 3
}

Response

{
  "places": [
    {
      "id": "ChIJcWGw3Yp_j4AR2D2USclEBsQ",
      "types": [
        "cafe",
        "coffee_shop",
        "food",
        "point_of_interest"
      ],
      "location": {
        "latitude": 37.7821,
        "longitude": -122.4065
      },
      "displayName": {
        "text": "Blue Bottle Coffee",
        "languageCode": "en"
      },
      "primaryType": "cafe",
      "googleMapsUri": "https://maps.google.com/?cid=12345",
      "businessStatus": "OPERATIONAL",
      "formattedAddress": "66 Mint St, San Francisco, CA 94103"
    }
  ],
  "nextPageToken": "AbCdEf..."
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.92/ 1.00

Full OpenAPI schema with request/response types, clear pricing ($0.02/request), detailed documentation and guidance, and multiple payment protocol options are all present. The probe returned 405 because HEAD/GET were tried on a POST-only endpoint, which is expected behavior, not a liveness issue. The endpoint is well-documented within the comprehensive StableEnrich OpenAPI spec.

Warnings

  • Probe returned 405 because HEAD and GET were attempted on a POST-only endpoint; this does not indicate the endpoint is down but direct 402 challenge was not captured for this specific path.

Citations

Provenance

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

Agent access