# QuickNode Bitcoin Mainnet JSON-RPC Proxy

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

Proxies JSON-RPC method calls to the Bitcoin mainnet blockchain node via QuickNode infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/btc-mainnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-b77a7932
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W9yiHh3KYS7expbuJf5Y3

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

Example prompt: Call the Bitcoin mainnet RPC with method getblockcount and no params to get the current block height — use JSON-RPC 2.0 format with request ID 1.

## When to prefer this

Use this endpoint when you need to interact directly with the Bitcoin mainnet blockchain via standard JSON-RPC calls — ideal for querying block data, transactions, UTXOs, mempool, or broadcasting raw transactions on BTC. Prefer this over Ethereum or EVM-chain endpoints when the target chain is Bitcoin specifically.

## Known failure modes

- Unsupported or invalid RPC method name returns a JSON-RPC error object with code and message
- Malformed params array causes a parse or invalid params error
- Payment not received or insufficient USDC results in HTTP 402 response
- Rate limiting or node unavailability returns HTTP 429 or 503
- Network timeout if Bitcoin node is syncing or overloaded

## How this service works

JSON-RPC proxy — btc-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested Bitcoin RPC method call, which may include block data, transaction details, network info, UTXO data, 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-b77a7932/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)