# QuantaFlow Google Local Services SERP API

> QuantaFlow Google Local Services 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-20).

Fetches Google Local Services search results (ads/listings) via a pay-per-call x402 micropayment gateway

## Facts

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

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-services-serp-api-dd2d3425 -d '<json body>'
```

Example prompt: Search Google Local Services for licensed plumbers in Austin, TX and return the top listings with their ratings and contact info.

## When to prefer this

Use this endpoint when you need Google Local Services-specific results (verified, licensed/insured providers with Google guarantee badges) rather than general Google Maps or organic web results. Ideal for agents that need structured local professional listings with ratings and contact info at very low per-call cost ($0.01 USDC). Prefer over general SERP APIs when the use case is specifically home services, professional contractors, or Google-verified local providers.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted — request is rejected before proxying
- Upstream SERP error: Google Local Services returns no results for the query/location combination
- Invalid query parameters: malformed path or query object causes upstream request failure
- Rate limiting: upstream provider throttles requests for high-volume queries
- Empty results: location or service category has no Google Local Services listings

## 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 Services SERP response, including local service provider listings with business names, star ratings, number of reviews, contact information, service categories, and ad placements, passed through as-is after successful x402 micropayment.

## 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-services-serp-api-dd2d3425/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)