# QuantaFlow SERP Google Ads API (x402)

> QuantaFlow SERP Google Ads API (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-17).

Retrieves Google Ads search engine results page (SERP) data via a pay-per-call x402 micropayment gateway at $0.01 USDC per request.

## Facts

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

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-serp-google-ads-api-x402-9bf4980d -d '<json body>'
```

Example prompt: Search Google Ads SERP for 'best running shoes 2024' and show me what paid ads and listings are appearing right now — I need it via the QuantaFlow micropayment gateway.

## When to prefer this

Choose this endpoint when you need pay-per-call Google Ads SERP data with no subscription commitment, particularly in Web3/DeFi-native agent workflows that support the x402 micropayment protocol. Ideal for sporadic or burst SERP lookups at $0.01 USDC per call where setting up a full SerpAPI or DataForSEO subscription is overkill. Prefer alternatives like SerpAPI or Bright Data for high-volume continuous scraping needs.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment header missing/invalid returns 402 Payment Required
- Invalid path or query parameters result in upstream error passed through
- Rate limiting or upstream Google Ads SERP provider unavailability returns 5xx
- Malformed JSON body causes request forwarding failure
- Empty or ambiguous search query may return sparse or no ad results

## How this service works

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

## Output

The upstream Google Ads SERP response body is passed through directly after successful x402 micropayment verification, typically including paid ad listings, organic results, ad copy, URLs, and related SERP features in the format returned by the underlying SERP data provider.

## 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-serp-google-ads-api-x402-9bf4980d/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)