# QuantaFlow Google Flights SERP Search

> QuantaFlow Google Flights 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-11).

Searches Google Flights via a pay-per-call x402 gateway, returning flight search results for given routes and dates

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/serp-google-flights?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-flights-serp-search-ec3f14c2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J5bkV6eUN2n0z1SUiPOP7

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-flights-serp-search-ec3f14c2 -d '<json body>'
```

Example prompt: Search Google Flights for round-trip flights from New York (JFK) to London (LHR), departing June 15 and returning June 22, for 2 passengers in economy class — show me the best options with prices.

## When to prefer this

Choose this endpoint when you need programmatic access to Google Flights search results with micropayment-based access (no subscription required), especially in web3/DeFi agent workflows that support x402 payment protocol. Ideal for one-off or low-frequency flight searches where a $0.01 per-call cost model is preferable to a monthly API subscription.

## Known failure modes

- Invalid or unrecognized airport codes return no results or an error
- Dates in the past or malformed date formats may cause upstream errors
- No flights available for the requested route/date combination returns empty results
- Payment failure via x402 protocol blocks the request before it reaches the upstream
- Upstream SERP provider rate limit or timeout causes a 5xx passthrough error
- Malformed JSON body causes request processing failure

## How this service works

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

## Output

Returns Google Flights search engine results including available flights matching the query, with details such as airline, price, departure and arrival times, flight duration, number of stops, and flight numbers, passed through directly from the upstream SERP data source.

## 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-flights-serp-search-ec3f14c2/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)