# QuantaFlow x402 API Gateway — Alchemy opBNB Mainnet

> QuantaFlow x402 API Gateway — Alchemy opBNB 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-23).

Proxies requests to the Alchemy opBNB Mainnet RPC/API through an x402 micropayment gateway, charging $0.01 USDC per call.

## Facts

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

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-alchemy-opbnb-mainnet-a7ff8901 -d '<json body>'
```

Example prompt: Fetch the latest block number from opBNB mainnet using the Alchemy gateway — just call eth_blockNumber on the mainnet path.

## When to prefer this

Choose this endpoint when you need pay-as-you-go, no-subscription access to opBNB Mainnet blockchain data via Alchemy's RPC infrastructure. Ideal for agents that make infrequent or unpredictable calls to opBNB and want to avoid committing to an Alchemy API key or monthly plan. Best suited for web3 agents already operating in the x402 micropayment ecosystem on BNB's layer-2 network.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment header returns 402 Payment Required
- Invalid path: unrecognized Alchemy API path returns upstream 404 or error
- Malformed request body: invalid JSON or unsupported RPC method returns Alchemy error response
- Network unavailability: Alchemy or opBNB node downtime causes 502/503 errors
- Rate limiting: upstream Alchemy rate limits may cause 429 responses

## How this service works

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

## Output

The raw upstream response from Alchemy's opBNB Mainnet API is passed through verbatim — typically a JSON-RPC response containing blockchain data such as block details, transaction receipts, account balances, or contract call results. The content type mirrors whatever Alchemy returns.

## 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-alchemy-opbnb-mainnet-a7ff8901/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)