# QuantaFlow Google Images SERP Search

> QuantaFlow Google Images 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-21).

Performs a Google Images search query and returns image results via the x402 micropayment-gated API gateway

## Facts

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

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-images-serp-search-9709960a -d '<json body>'
```

Example prompt: Search Google Images for 'cherry blossom festival Tokyo' and give me the top image results including their URLs and titles.

## When to prefer this

Choose this endpoint when you need programmatic access to Google Images search results and are operating in a web3/crypto-native environment where micropayment-per-call billing via x402/USDC is preferred over API key subscriptions. Suitable for agents that perform on-demand image searches without requiring a long-term SERP API subscription.

## Known failure modes

- Payment failure — insufficient USDC balance or x402 payment header invalid, returns 402 Payment Required
- Invalid query parameters — malformed query object or path causes upstream error
- Rate limiting — upstream SERP provider throttles excessive requests
- Empty results — search query returns no matching images
- Network timeout — upstream Google Images SERP proxy unreachable
- Invalid JSON body — malformed body string 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 Images SERP response containing image results including image URLs, thumbnail URLs, titles, source domains, and associated metadata for the queried search term, passed through after successful x402 micropayment authorization.

## 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-images-serp-search-9709960a/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)