# QuickNode JSON-RPC Proxy — Berachain Mainnet

> QuickNode JSON-RPC Proxy — Berachain 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 calls to the Berachain mainnet blockchain, enabling queries and interactions such as reading blocks, balances, and submitting transactions.

## Facts

- Endpoint: POST https://x402.quicknode.com/bera-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-4cb390d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c0NGNnZ_vbbkGRh6n_rbr

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

Example prompt: Call eth_getBalance on Berachain mainnet for wallet address 0xAbC123... using JSON-RPC 2.0 and tell me the current BERA balance.

## When to prefer this

Use this endpoint when you need direct JSON-RPC access to Berachain mainnet specifically — ideal for reading on-chain state, submitting transactions, calling smart contracts, or any EVM-compatible operation on the Berachain network. Prefer over generic RPC providers when you need reliable, paid-tier access via x402 micropayments.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (Method not found)
- Malformed params array causes -32602 (Invalid params)
- Payment not included or insufficient results in HTTP 402 Payment Required
- Network congestion or node unavailability may cause timeout or -32603 (Internal error)
- Unsupported method for Berachain returns method not supported error

## How this service works

JSON-RPC proxy — bera-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block data, balance in hex, transaction receipt, contract return value) 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-4cb390d6/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)