# QuantaFlow x402 API Gateway – Binance Proxy

> QuantaFlow x402 API Gateway – Binance Proxy 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-13).

Proxies requests to Binance's API through an x402 micropayment-gated gateway, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/binance?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-binance-proxy-20cc962e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lm4WOlx-5ERvc7guwaMbD

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-binance-proxy-20cc962e -d '<json body>'
```

Example prompt: Fetch the current BTC/USDT ticker price from Binance — use the /api/v3/ticker/price path with symbol=BTCUSDT.

## When to prefer this

Choose this endpoint when you need pay-per-call access to Binance market data without a Binance API key or subscription, especially in web3/DeFi agent workflows where micropayment settlement via x402 protocol and USDC is preferred over traditional API key management. Suitable for low-frequency queries where $0.01/call economics make sense.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment header missing/invalid — gateway rejects request before forwarding
- Invalid path: requested Binance API path does not exist — upstream returns 404
- Rate limiting: Binance upstream rate limits triggered — upstream returns 429
- Invalid symbol or parameter: Binance rejects malformed query parameters — upstream returns 400 with error message
- Network timeout: upstream Binance API unreachable — gateway may return 5xx

## How this service works

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

## Output

The raw upstream Binance API response body, passed through as-is after successful x402 micropayment authorization. Includes whatever JSON data Binance returns for the requested path (e.g. price, order book, candlesticks, exchange info), along with the original content type.

## 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-binance-proxy-20cc962e/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)