# QuantaFlow x402 API Gateway — Rapid ZoneBot Crypto Data

> QuantaFlow x402 API Gateway — Rapid ZoneBot Crypto Data 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 requests to the Rapid ZoneBot Crypto Data API upstream service via x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-zonebot-crypto-data-api?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-x402-api-gateway-rapid-zonebot-crypto-data-f7d2236d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vaZMPHaBIRklEZTZReyrR

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-x402-api-gateway-rapid-zonebot-crypto-data-f7d2236d -d '<json body>'
```

Example prompt: Can you fetch the current price and 24-hour volume for Bitcoin and Ethereum from the ZoneBot crypto data API, paying per request with USDC?

## When to prefer this

Choose this endpoint when you need per-call access to ZoneBot crypto market data without a subscription, and your agent can handle x402 USDC micropayments. Ideal for low-frequency or bursty crypto data queries where pay-per-use is more economical than a monthly API plan. Best suited for agents with an on-chain wallet that supports the x402 payment protocol.

## Known failure modes

- Insufficient USDC balance causes payment failure and 402 response
- Invalid or missing path parameter returns upstream 404
- Malformed query object causes upstream API error
- Upstream Rapid ZoneBot API downtime returns gateway error
- Incorrect method value causes forwarding mismatch
- Rate limiting from upstream API despite successful payment

## How this service works

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

## Output

The raw upstream response body from the Rapid ZoneBot Crypto Data API, including cryptocurrency prices, volumes, market caps, or other crypto market data, passed through after successful $0.01 USDC x402 payment. Response format mirrors the upstream API's native JSON structure.

## 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-x402-api-gateway-rapid-zonebot-crypto-data-f7d2236d/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)