# Pocket Network Ethereum Mainnet JSON-RPC

> Pocket Network Ethereum 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 JSON-RPC access to Ethereum mainnet via Pocket Network's decentralised relay network, billed per-request in USDC with no API key required.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/eth?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-ethereum-mainnet-json-rpc-fd3c890d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o5pBzukkdprbVWAzExNcj

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-ethereum-mainnet-json-rpc-fd3c890d -d '<json body>'
```

Example prompt: What's the current ETH balance of address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum mainnet, and what's the latest block number?

## When to prefer this

Choose this endpoint when you need permissionless, keyless read access to Ethereum mainnet state and are comfortable paying per-request in USDC via x402. It is ideal for agents that must avoid API key management overhead, need decentralised redundancy across multiple relay nodes, or are making sporadic rather than high-volume queries. Prefer alternatives with dedicated API keys or subscription plans if you expect very high request volumes where per-call USDC costs add up significantly.

## Known failure modes

- Invalid or unsupported JSON-RPC method returns a JSON-RPC error with code -32601
- Malformed params cause a -32602 invalid params error
- Write methods (eth_sendRawTransaction) are rejected as this is read-only access
- Rate limiting or supplier unavailability may cause transient errors
- Requesting a very old archive state may fail if suppliers don't retain full history
- Payment failure or insufficient USDC balance results in HTTP 402 before the RPC call is attempted

## How this service works

Pay-per-call access to Pocket Network services. No account, no API key.

## Output

Returns a standard Ethereum JSON-RPC response object containing the requested data — such as a balance in wei, block object, transaction receipt, logs array, gas estimate, or fee history — depending on the method called. All responses are read-only snapshots of Ethereum mainnet state as seen by Pocket Network's decentralised supplier set.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_capabilities",
    "eth_chainId",
    "eth_coinbase",
    "eth_config",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockAccessList",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getProof",
    "eth_getStorageAt",
    "eth_getStorageValues",
    "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",
    "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": "eth",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-ethereum-mainnet-json-rpc-fd3c890d/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)