# QuantaFlow x402 API Gateway — Infura BSC Mainnet

> QuantaFlow x402 API Gateway — Infura BSC Mainnet 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-18).

Proxies requests to Infura's Binance Smart Chain (BSC) Mainnet JSON-RPC endpoint via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/infura-bsc-mainnet?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-infura-bsc-mainnet-4344f7d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VO8AvnRiFCyoWijLbVusi

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-infura-bsc-mainnet-4344f7d3 -d '<json body>'
```

Example prompt: Query the BSC mainnet via Infura to get the current BNB balance for wallet address 0xAbC...123 — use the eth_getBalance JSON-RPC call with the latest block tag.

## When to prefer this

Choose this endpoint when you need pay-per-use access to Infura's BSC Mainnet JSON-RPC without managing an Infura API key subscription — ideal for agents making infrequent or unpredictable BSC queries where a $0.01/call model is more cost-efficient than a monthly plan. Prefer over raw Infura direct access when operating in an x402-native payment context.

## Known failure modes

- Payment failure: x402 micropayment of $0.01 USDC not fulfilled, request blocked before proxying
- Invalid JSON-RPC method: upstream returns a JSON error object with code -32601
- Malformed request body: gateway may reject or upstream returns parse error
- BSC node unavailable: Infura outage causes 502/503 upstream error
- Rate limit exceeded on upstream Infura endpoint
- Invalid wallet address or transaction hash returns empty or null result

## How this service works

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

## Output

The raw JSON-RPC response body from Infura's BSC Mainnet node, passed through transparently — including fields like result, id, jsonrpc, and any error object if the call fails. Response content type mirrors the upstream.

## 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-infura-bsc-mainnet-4344f7d3/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)