# Google Maps Review Fetch — fetcher.sh

> Google Maps Review Fetch — fetcher.sh is a paid API for AI agents from google-maps.fetcher.sh, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches a single Google Maps review by its ID, returning review text and metadata, paid per call in USDC via x402.

## Facts

- Endpoint: GET https://google-maps.fetcher.sh/api/review/%7Bid%7D
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/google-maps-review-fetch-fetcher-sh-54dc285a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QyPHYO9rLNykB1LcxlM0_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability google-maps-review-fetch-fetcher-sh-54dc285a
```

Example prompt: Can you fetch the Google Maps review with ID 'ChIJN1t_tDeuEmsRUsoyG83frY3' and show me what the reviewer said and what rating they gave?

## When to prefer this

Choose this endpoint when you need to fetch a specific, known Google Maps review by its ID without setting up a Google Maps API account, OAuth credentials, or a subscription. It is ideal for ad-hoc lookups, pay-per-use pipelines, or when you want to avoid Google API quotas and billing setup. Prefer it over direct Google Maps API calls when you want instant access with crypto micropayments and no account management overhead.

## Known failure modes

- Invalid or non-existent review ID returns a 404 or empty response
- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required error
- Review may have been deleted from Google Maps since indexing, returning no content
- Rate limiting or upstream Google Maps data unavailability causing temporary errors
- Malformed review ID format causing a 400 Bad Request

## How this service works

Google Maps (gmaps) data and scraping API: Place search, place details, and reviews. 4 REST endpoints from $0.005 per call — no account, no OAuth, no subscription. Pay with x402 (USDC on Base, Polygon, Arbitrum, Monad or Solana) or prepaid credits.

## Output

Returns structured data for the requested Google Maps review, including the review text body, star rating, reviewer name, review date, and any associated place or author metadata available from the Google Maps listing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/google-maps-review-fetch-fetcher-sh-54dc285a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from google-maps.fetcher.sh](https://www.zero.xyz/host/google-maps.fetcher.sh/llms.txt)