# QuantaFlow SERP Bing Maps Search via x402

> QuantaFlow SERP Bing Maps Search 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).

Proxies Bing Maps search/SERP queries through a pay-per-call x402 payment gateway at $0.01 USDC per request

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/serp-bing-maps?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-serp-bing-maps-search-via-x402-aa3aa29a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uyt0VDoSVJu5A_G2VE8fi

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-bing-maps-search-via-x402-aa3aa29a -d '<json body>'
```

Example prompt: Search Bing Maps for coffee shops near 123 Main Street, Seattle and return the top results including addresses and ratings.

## When to prefer this

Choose this endpoint when you need programmatic access to Bing Maps search or SERP data via a pay-per-call micropayment model using the x402 protocol, particularly in Web3 or DeFi agent contexts where on-chain USDC payments are preferred over traditional API key subscriptions. Prefer this over direct Bing Maps API access when you want to avoid managing API keys or subscriptions and instead pay $0.01 USDC per query.

## Known failure modes

- Payment failure or insufficient USDC balance causes request to be rejected before forwarding
- Invalid or malformed path/query parameters result in upstream Bing Maps API errors
- Upstream Bing Maps API rate limits or outages return passthrough error responses
- Incorrect JSON body format for POST requests may cause upstream parsing errors
- Missing required query parameters for specific Bing Maps endpoints return 400-level errors

## How this service works

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

## Output

Returns the upstream Bing Maps SERP/search API response passed through after successful x402 micropayment, typically including location results, place details, coordinates, business listings, or map search data depending on the query path used.

## 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-bing-maps-search-via-x402-aa3aa29a/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)