# QuantaFlow Bing Image Search (SERP) via x402

> QuantaFlow Bing Image Search (SERP) 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-14).

Search Bing for images using a SERP query and return image results, billed per-call via the x402 micropayment protocol at $0.01 USDC.

## Facts

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

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-bing-image-search-serp-via-x402-a2308695 -d '<json body>'
```

Example prompt: Search Bing images for 'golden retriever puppies playing' 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 Bing image search results and want to pay per-call via x402 micropayments (USDC on-chain) without managing a traditional API key subscription. It is well-suited for AI agents that need to gather visual references, find image URLs by keyword, or enrich content workflows with Bing image data on a low-volume or ad-hoc basis.

## Known failure modes

- Payment failure or insufficient USDC balance — x402 payment not processed, request rejected before reaching Bing
- Invalid or missing query parameter — empty or malformed search query returns no results or upstream error
- Bing API rate limit or upstream error — gateway passes through Bing error response
- Malformed request body/path — incorrect JSON structure causes gateway routing failure
- Network timeout — upstream Bing service or gateway unresponsive

## How this service works

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

## Output

The upstream Bing image SERP response is passed through directly after successful x402 micropayment. Typically includes an array of image result objects containing image URLs, thumbnail URLs, titles, source page URLs, dimensions, and other Bing image search metadata fields.

## 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-bing-image-search-serp-via-x402-a2308695/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)