# QuantaFlow Google Maps Places Autocomplete

> QuantaFlow Google Maps Places Autocomplete 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-24).

Returns Google Maps place autocomplete suggestions for a partial address or location query via x402 micropayment gateway

## Facts

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

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-maps-places-autocomplete-9f36a2fc -d '<json body>'
```

Example prompt: Can you autocomplete the partial address '1600 Pennsylvan' and give me the top Google Maps place suggestions for it?

## When to prefer this

Use this endpoint when you need Google Maps-quality place autocomplete predictions and want to pay per-call via x402 micropayments in USDC with no API key management. Prefer this over direct Google Maps API calls when operating in a web3/agent context where x402 payment rails are already set up, or when you want a simple pay-as-you-go model without subscription overhead.

## Known failure modes

- Payment failure: x402 payment not accepted or insufficient USDC balance returns a 402 error
- Invalid query: missing or malformed partial input returns no predictions or an upstream error
- Upstream API error: Google Maps Places API quota exceeded or key invalid returns 5xx or error response
- Malformed path/query parameters: incorrect routing to upstream API returns unexpected response
- Network timeout: Vercel edge or upstream latency causes timeout

## 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 Maps Places Autocomplete API response, including an array of place predictions with description, place_id, and structured formatting for each matching suggestion.

## 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-maps-places-autocomplete-9f36a2fc/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)