# 402rpc Ethereum JSON-RPC

> 402rpc Ethereum JSON-RPC is a paid API for AI agents from 402rpc.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-16).

Executes Ethereum mainnet JSON-RPC calls (eth_, net_, web3_ methods) via a pay-per-call independently operated full node, with no API key required.

## Facts

- Endpoint: POST https://402rpc.com/rpc?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/402rpc-ethereum-json-rpc-4662478a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wpyd8_llIWG31qmnHQWz5

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 402rpc-ethereum-json-rpc-4662478a -d '<json body>'
```

Example prompt: What's the current ETH balance of 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum mainnet right now? Use eth_getBalance with the latest block tag.

## When to prefer this

Choose this endpoint when you need permissionless, no-account Ethereum mainnet JSON-RPC access and are comfortable with micropayment-per-call billing via x402/USDC. Ideal for agents that make infrequent or unpredictable Ethereum queries without wanting to manage API keys or subscriptions. Not suitable for archive/historical state queries or methods outside eth_, net_, and web3_ namespaces.

## Known failure modes

- Historical state queries (pre-Merge block state) are refused without charge
- eth_getLogs range exceeding 10,000 blocks returns an error
- Unsupported method prefixes (e.g. debug_, trace_) result in method-not-found errors
- Malformed JSON-RPC request returns parse or invalid-request error
- Insufficient USDC payment results in 402 Payment Required before processing
- Network congestion may delay raw transaction relay via public relays

## How this service works

Ethereum mainnet JSON-RPC from an independently operated full node. One call per payment, no account or API key. Serves eth_, net_ and web3_ methods. Blocks, transactions, receipts and logs from the Merge (block 15537394) onward. Current state only, not an archive node: historical state calls are refused, not charged. eth_getLogs capped at 10000 blocks. Raw transactions go out via public relays. Price scales with method cost.

## Output

Returns a standard JSON-RPC 2.0 response object containing either a 'result' field with the requested data (block, balance, receipt, logs, call output, etc.) or an 'error' object with code and message. Historical state before the Merge (block 15537394) is not available; eth_getLogs is capped at a 10,000-block range.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "string",
    "number"
   ]
  },
  "method": {
   "type": "string",
   "examples": [
    "eth_blockNumber",
    "eth_getBalance",
    "eth_call",
    "eth_getLogs"
   ],
   "description": "JSON-RPC method. eth_, net_ and web3_ only."
  },
  "params": {
   "type": "array",
   "description": "Positional parameters for the method."
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/402rpc-ethereum-json-rpc-4662478a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402rpc.com](https://www.zero.xyz/host/402rpc.com/llms.txt)