# QuickNode JSON-RPC Proxy — Bitcoin Cash Mainnet

> QuickNode JSON-RPC Proxy — Bitcoin Cash Mainnet 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 method calls to the Bitcoin Cash (BCH) mainnet blockchain node via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/bch-mainnet/
- 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-6e1bfc96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IANJtL5E2IWYvw_T04QkG

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-6e1bfc96 -d '<json body>'
```

Example prompt: Call the Bitcoin Cash mainnet node to get the current block height — use the getblockcount JSON-RPC method on QuickNode's BCH mainnet endpoint.

## When to prefer this

Choose this endpoint when you need to interact with the Bitcoin Cash (BCH) mainnet blockchain specifically, as opposed to other chains. Use it for querying BCH block data, transactions, UTXOs, or broadcasting BCH transactions. Prefer this over general Web3 providers when you need reliable, low-latency BCH node access without managing your own node infrastructure.

## Known failure modes

- Invalid JSON-RPC method name returns an error response with code -32601
- Missing or malformed params array causes a -32602 invalid params error
- Payment of $10 USDC not provided results in 402 Payment Required
- Node unavailability or network timeout returns a 503 or connection error
- Calling Ethereum-specific methods (e.g. eth_blockNumber) on a BCH node will return an error as BCH uses different RPC methods

## How this service works

JSON-RPC proxy — bch-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested BCH node method, including block data, transaction details, balance information, or other blockchain state depending on the method called.

## 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-6e1bfc96/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)