# QuantaFlow Google Hotels Autocomplete (via x402)

> QuantaFlow Google Hotels Autocomplete (via x402) 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-11).

Returns Google Hotels autocomplete suggestions for a search query, accessed via x402 micropayment gateway.

## Facts

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

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-autocomplete-via-x402-c14e2849 -d '<json body>'
```

Example prompt: Can you get me Google Hotels autocomplete suggestions for the partial query 'Marriott New York' so I can populate a hotel search typeahead dropdown?

## When to prefer this

Choose this endpoint when you need real-time Google Hotels autocomplete suggestions to power a typeahead or search-as-you-type hotel UI, and when you want to pay per-call in USDC via the x402 protocol without managing a SerpApi subscription. It is ideal for lightweight, low-volume or agent-driven hotel search flows where micropayments are acceptable and no long-term API key management is desired.

## Known failure modes

- Payment failure if USDC balance is insufficient or x402 handshake fails
- Empty or no suggestions returned for very obscure or misspelled queries
- Upstream SerpApi or Google Hotels rate limit or API key exhaustion causing 5xx errors
- Malformed query body results in 400 bad request from upstream
- Network timeout if upstream service is slow or unavailable

## How this service works

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

## Output

A pass-through of the upstream Google Hotels autocomplete API response, containing a list of suggested hotel names, properties, or locations matching the partial query string, along with any metadata such as place IDs or descriptions returned by the underlying SerpApi/Google Hotels autocomplete service.

## 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-autocomplete-via-x402-c14e2849/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)