# QuantaFlow x402 API Gateway – Rapid Binance43

> QuantaFlow x402 API Gateway – Rapid Binance43 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-11).

Proxies requests to a Binance-related web3/DeFi upstream service via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-binance43?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapid-binance43-337f8227
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jFAFibNLmy4xjJ2P1Cqwm

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-binance43-337f8227 -d '<json body>'
```

Example prompt: Hit the Binance exchange info endpoint and get me the current trading rules and symbol list — route it through the QuantaFlow x402 gateway, path '/exchangeInfo', GET method, no extra query params needed.

## When to prefer this

Choose this endpoint when you need pay-per-call access to Binance market data without managing your own Binance API keys, when your agent workflow uses the x402 micropayment protocol natively, or when you want sub-cent per-query pricing for crypto market lookups in a DeFi/web3 context.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment header returns 402 Payment Required
- Invalid path: unrecognized Binance endpoint path returns upstream 404 or error JSON
- Rate limiting: Binance upstream may throttle requests returning 429
- Malformed query parameters: invalid symbol or parameter combinations return Binance error codes
- Gateway unavailability: Vercel cold start or downtime returns 500 or timeout

## 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 (JSON) passed through as-is after the x402 USDC micropayment is settled, along with the upstream content-type header. The agent receives whatever the Binance endpoint returns for the given path and parameters.

## 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-binance43-337f8227/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)