# QuantaFlow Google Hotels Reviews SERP API

> QuantaFlow Google Hotels Reviews SERP API is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Fetches Google Hotels reviews search engine results page (SERP) data via a pay-per-call x402 micropayment gateway

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/serp-google-hotels-reviews?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-google-hotels-reviews-serp-api-e5e0ad5e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kVeqKInEWIWGScWn5kl_A

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 quantaflow-google-hotels-reviews-serp-api-e5e0ad5e -d '<json body>'
```

Example prompt: Can you pull the Google Hotels reviews for the Marriott Times Square in New York — I want to see what guests are saying about it recently?

## When to prefer this

Choose this endpoint when you need Google Hotels review data specifically (guest ratings, review text, aggregate scores) for a named hotel property and want to pay per-call via x402 USDC micropayments without a subscription. Prefer this over general web scraping when structured SERP-formatted hotel review data is required, or over a full SerpApi subscription when call volume is low and pay-as-you-go is preferable.

## Known failure modes

- Payment failure (402): insufficient USDC balance or x402 payment not accepted, request blocked
- Invalid query parameters: malformed path or query object results in upstream error
- Hotel not found: query matches no Google Hotels listing, returns empty or error response
- Rate limiting: upstream SERP provider throttles requests, returns 429
- Gateway timeout: upstream latency causes request to fail
- Invalid JSON body: malformed body string causes parsing error

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

Returns the upstream Google Hotels reviews SERP data as passed through by the QuantaFlow gateway — typically includes review text, reviewer names, star ratings, review dates, and aggregate rating metadata for the queried hotel property. Content type and body are passed through directly from the upstream source.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-google-hotels-reviews-serp-api-e5e0ad5e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)