# NodeFlare BNB Chain RPC (Chain 56)

> NodeFlare BNB Chain RPC (Chain 56) is a paid API for AI agents from rpc.nodeflare.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-10).

Provides full JSON-RPC access to BNB Chain (chain 56) via NodeFlare's bare-metal archive nodes, supporting all standard and advanced methods including eth_getLogs, eth_call, trace, and debug, billed per request in USDC with no account required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/bnb/x402?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeflare-bnb-chain-rpc-chain-56-eff90fff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XXdiYrrLVlEoDGF9bDuzr

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 nodeflare-bnb-chain-rpc-chain-56-eff90fff -d '<json body>'
```

Example prompt: Call eth_getLogs on BNB Chain to fetch all Transfer events from contract 0x55d398326f99059fF775485246999027B3197955 between blocks 38000000 and 38001000.

## When to prefer this

Choose this endpoint when you need reliable, full-featured JSON-RPC access to BNB Chain (chain 56) specifically, including archive-depth data, trace, and debug methods, without managing API keys or subscriptions. Ideal for AI agents that pay per call in USDC via x402 and need indexing, event queries, or transaction simulation on BSC. Prefer this over generic RPC providers when you need no-account access with deterministic per-call pricing.

## Known failure modes

- Method not supported: error if an unsupported RPC method is requested
- Invalid params: error if required params are missing or malformed
- Payment failure: x402 payment not accepted or insufficient USDC balance
- Block not found: requested block number does not exist yet
- Rate or compute limit: heavy debug/trace calls may return timeout or compute-unit errors
- Reverted call: eth_call returns revert reason if the simulated transaction would revert

## How this service works

BNB Chain RPC (chain 56): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy calls priced by compute units.

## Output

A standard JSON-RPC 2.0 response object containing the result field populated with the requested on-chain data (block, transaction, log array, call return value, trace object, etc.) or an error object with code and message if the call failed. All standard Ethereum JSON-RPC response formats apply, including archive-depth data for trace and debug methods.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nodeflare-bnb-chain-rpc-chain-56-eff90fff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rpc.nodeflare.app](https://www.zero.xyz/host/rpc.nodeflare.app/llms.txt)