# QuantaFlow Google Local SERP Search

> QuantaFlow Google Local SERP Search 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-14).

Fetches Google local search results (SERP) via a pay-per-call x402 micropayment gateway for $0.01 USDC per request

## Facts

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

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-local-serp-search-e7145fae -d '<json body>'
```

Example prompt: Search Google local results for 'pizza delivery' in Austin, Texas and give me the top business listings including names, addresses, and ratings.

## When to prefer this

Choose this endpoint when you need pay-per-use, frictionless Google Local SERP data via the x402 micropayment protocol without a traditional API subscription. Ideal for AI agents that need on-demand local business search results at $0.01 per call with no upfront commitment, especially in web3/DeFi-native stacks that already handle USDC payments.

## Known failure modes

- Payment failure or insufficient USDC balance returns a 402 Payment Required error
- Invalid or malformed query parameters result in an upstream error response
- Rate limiting or quota exhaustion on the upstream Google SERP provider
- Empty results if the query/location combination yields no local listings
- Network timeout if upstream Google SERP service is slow or unavailable
- Malformed JSON body causes request parsing failure

## How this service works

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

## Output

Returns the upstream Google Local SERP response data passed through after payment, typically including business names, addresses, ratings, reviews count, phone numbers, hours, and other local listing metadata for the queried location and keyword.

## 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-local-serp-search-e7145fae/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)