# QuickNode JSON-RPC Proxy — BSC Testnet

> QuickNode JSON-RPC Proxy — BSC Testnet is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-15).

Proxies JSON-RPC calls to the Binance Smart Chain (BSC) testnet via QuickNode's node infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/bsc-testnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-5b297517
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RbaGQNLbKsPsxctnTSfzr

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 quicknode-5b297517 -d '<json body>'
```

Example prompt: Call eth_blockNumber on BSC testnet using QuickNode's JSON-RPC proxy to get the latest block height — use jsonrpc 2.0 with request id 1 and no params.

## When to prefer this

Use this endpoint when you need to interact with the Binance Smart Chain testnet specifically — for testing BEP-20 tokens, smart contract deployments, or BSC-compatible dApp logic without spending real BNB. Prefer this over mainnet endpoints during development and testing phases.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 Method not found
- Malformed params array causes -32602 Invalid params error
- Network congestion or node unavailability may return -32603 Internal error
- Payment failure (insufficient USDC) results in 402 Payment Required before the call is processed
- Unsupported method for BSC testnet returns method-specific error

## How this service works

JSON-RPC proxy — bsc-testnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method (e.g., block number, transaction receipt, contract call output, balance) or an error object with code and message if the call fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "jsonrpc",
  "method"
 ],
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ],
   "description": "Request identifier"
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
  },
  "params": {
   "type": "array",
   "description": "Method parameters"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "error": {
   "type": "object",
   "properties": {
    "code": {
     "type": "integer"
    },
    "message": {
     "type": "string"
    }
   }
  },
  "result": {
   "description": "RPC result (type varies by method)"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-5b297517/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quicknode.com](https://www.zero.xyz/host/x402.quicknode.com/llms.txt)