# QuantaFlow Google Flights Autocomplete via x402

> QuantaFlow Google Flights Autocomplete via 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-10).

Returns Google Flights destination/airport autocomplete suggestions for a given search query, paid per-call via the x402 micropayment protocol.

## Facts

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

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-autocomplete-via-x402-b30feaf9 -d '<json body>'
```

Example prompt: What are the Google Flights autocomplete suggestions for airports or destinations matching 'Los Ang'? I need the top results including IATA codes.

## When to prefer this

Choose this endpoint when you need Google Flights-specific autocomplete suggestions (airports, cities, destination names) and want to pay per-call via x402 USDC micropayments without a subscription. Prefer it over scraping or generic SERP APIs when you specifically need the flight-oriented destination/airport lookup that Google Flights surfaces, especially for building travel search UIs or validating user-typed flight destinations.

## Known failure modes

- Payment failure if x402 USDC balance is insufficient — returns 402 Payment Required
- Invalid or missing query parameters — upstream returns empty or error response
- Upstream Google Flights SERP API unavailable — gateway passes through 5xx error
- Malformed path or query object — request not forwarded correctly
- Rate limiting by upstream SERP provider — 429 or throttled response

## How this service works

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

## Output

The proxied upstream response from the Google Flights autocomplete SERP endpoint, containing an array of matching airport names, city names, IATA codes, and related location metadata for the input query string.

## 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-autocomplete-via-x402-b30feaf9/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)