# QuickNode JSON-RPC Proxy — Berachain Bepolia Testnet

> QuickNode JSON-RPC Proxy — Berachain Bepolia 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 Berachain Bepolia testnet, enabling blockchain queries and transactions via standard Ethereum-compatible RPC methods.

## Facts

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

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

Example prompt: Call eth_blockNumber on the Berachain Bepolia testnet using QuickNode's JSON-RPC proxy to get the latest block number.

## When to prefer this

Use this endpoint when you need to interact specifically with the Berachain Bepolia testnet (not mainnet) for development, testing, or querying testnet state. Prefer this over other RPC providers when QuickNode's reliability and latency are required and you are working within the x402 micropayment ecosystem.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code and message
- Malformed params array causes parse or invalid params error
- Payment not provided or insufficient results in 402 Payment Required
- Network congestion on Bepolia testnet may cause timeouts
- Requesting data for non-existent blocks or transactions returns null result

## How this service works

JSON-RPC proxy — bera-bepolia

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number, transaction hash, call return value, balance in wei) or an error object if the call failed.

## 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-36cba57c/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)