# Pocket Network – Berachain Mainnet JSON-RPC

> Pocket Network – Berachain Mainnet JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-03).

Provides read-only Ethereum-compatible JSON-RPC access to Berachain mainnet via Pocket Network's decentralised node supplier set, billed per-request in USDC with no API key required.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/bera?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-berachain-mainnet-json-rpc-a14ee13e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qkJBjKx0kHywYYEoTl6oR

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 pocket-network-berachain-mainnet-json-rpc-a14ee13e -d '<json body>'
```

Example prompt: What's the current BERA balance of wallet address 0xAbCd...1234 on Berachain mainnet? Use eth_getBalance with the latest block tag.

## When to prefer this

Choose this endpoint when you need permissionless, keyless read access to Berachain mainnet EVM state and want to pay per call in USDC without managing API keys or subscriptions. It is ideal for agents operating in trustless or multi-tenant environments where account creation is impractical. Prefer it over centralised RPC providers when decentralisation or censorship-resistance of the node layer matters.

## Known failure modes

- Invalid or unsupported method name returns a JSON-RPC error with code -32601
- Malformed params returns a JSON-RPC parse or invalid-params error (-32700 / -32602)
- Attempting a write method (e.g. eth_sendRawTransaction) is rejected as this is a read-only endpoint
- Insufficient USDC balance causes a 402 Payment Required response before the RPC call is made
- Berachain node temporary unavailability may return a 503 or upstream JSON-RPC internal error (-32603)
- Rate-limit or quota exhaustion may return a 429 Too Many Requests HTTP response

## How this service works

Read-only JSON-RPC access to Berachain mainnet, served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

## Output

A JSON-RPC 2.0 response object containing the result field with the requested chain data (e.g. balance as a hex string, block object, transaction receipt object, log array, hex-encoded bytecode, etc.) or an error object with code and message if the call fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "debug_getBadBlocks",
    "debug_getRawBlock",
    "debug_getRawHeader",
    "debug_getRawReceipts",
    "debug_getRawTransaction",
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_config",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "eth_getTransactionByBlockHashAndIndex",
    "eth_getTransactionByBlockNumberAndIndex",
    "eth_getTransactionByHash",
    "eth_getTransactionCount",
    "eth_getTransactionReceipt",
    "eth_getUncleByBlockHashAndIndex",
    "eth_getUncleByBlockNumberAndIndex",
    "eth_getUncleCountByBlockHash",
    "eth_getUncleCountByBlockNumber",
    "eth_maxPriorityFeePerGas",
    "eth_newBlockFilter",
    "eth_newFilter",
    "eth_newPendingTransactionFilter",
    "eth_simulateV1",
    "eth_syncing",
    "eth_uninstallFilter",
    "net_listening",
    "net_peerCount",
    "net_version",
    "txpool_status",
    "web3_clientVersion",
    "web3_sha3"
   ],
   "description": "JSON-RPC read method, e.g. eth_getBalance"
  },
  "params": {
   "description": "Parameters per the Ethereum JSON-RPC spec"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": 1,
   "result": false,
   "jsonrpc": "2.0"
  },
  "portal": {
   "serviceId": "bera",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-berachain-mainnet-json-rpc-a14ee13e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)