# BlockRun Ethereum JSON-RPC Endpoint

> BlockRun Ethereum JSON-RPC Endpoint is a paid API for AI agents from blockrun.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Executes Ethereum JSON-RPC calls (eth_blockNumber, eth_call, eth_getBalance, etc.) with per-call USDC micropayment via x402 protocol

## Facts

- Endpoint: POST https://blockrun.ai/api/v1/rpc/ethereum
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockrun-ethereum-json-rpc-endpoint-e176c005
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_skrq1XIH5mApsfA4iJQ_Q

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 blockrun-ethereum-json-rpc-endpoint-e176c005 -d '<json body>'
```

Example prompt: Check the current ETH balance for address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum mainnet — use eth_getBalance with the latest block tag.

## When to prefer this

Choose this endpoint when you need to query Ethereum on-chain data on a per-call pay-as-you-go basis without committing to a monthly subscription with providers like Infura or Alchemy. Particularly useful for AI agents that make sporadic or unpredictable RPC calls and want to pay in USDC micropayments via the x402 protocol. Best for read-only Ethereum JSON-RPC queries where cost predictability at $0.003/call is preferable to flat-rate subscriptions.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Insufficient USDC payment via x402 protocol results in 402 Payment Required response
- Network congestion or node unavailability may cause timeouts
- Unsupported EVM method or chain-specific method returns error
- Missing or invalid jsonrpc version field causes parse error

## How this service works

Pay for the outcome. One endpoint for every model, tool and data source an agent needs — each call priced before it runs, at the best value per dollar. 103 models and 100 data and tool APIs.

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested Ethereum RPC method — e.g. a hex-encoded balance, block number, transaction receipt object, or contract return value — along with the matching id field and any error details if the call failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string|number",
   "description": "JSON-RPC id"
  },
  "method": {
   "type": "string",
   "description": "Chain RPC method, e.g. eth_blockNumber, eth_call, eth_getBalance (EVM) or getSlot, getAccountInfo (Solana)."
  },
  "params": {
   "type": "array",
   "description": "Method-specific params."
  },
  "jsonrpc": {
   "type": "string",
   "description": "\"2.0\""
  }
 }
}
```

## More

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