# NodeFlare Ethereum Mainnet RPC (Chain 1)

> NodeFlare Ethereum Mainnet RPC (Chain 1) is a paid API for AI agents from rpc.nodeflare.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Executes arbitrary Ethereum mainnet JSON-RPC calls — including eth_getLogs, eth_call, trace, and debug — on NodeFlare's bare-metal archive nodes, billed per request in USDC via x402 with no API key required.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/eth/x402?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeflare-ethereum-mainnet-rpc-chain-1-0891cb6e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JYgXdO9QGwwQuPi8VIWKq

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 nodeflare-ethereum-mainnet-rpc-chain-1-0891cb6e -d '<json body>'
```

Example prompt: Call eth_getLogs on Ethereum mainnet for contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 from block 20000000 to 20001000, filtering for the Transfer event topic.

## When to prefer this

Choose this endpoint when you need direct, low-level Ethereum mainnet JSON-RPC access — especially archive methods like eth_getLogs over wide block ranges, debug_traceTransaction, or trace_* calls — without managing API keys or monthly subscriptions. It is ideal for AI agents that need pay-as-you-go, autonomous Ethereum data access billed in USDC via x402, and is particularly well-suited to indexing pipelines, event log queries, transaction simulations, and on-chain debugging tasks.

## Known failure modes

- Invalid or unsupported RPC method name returns a JSON-RPC error with code -32601
- Malformed params array causes -32602 invalid params error
- Requesting a pruned historical block on a non-archive path returns null or error
- Rate or compute-unit budget exceeded returns HTTP 402 or payment-required error
- Network or node unavailability returns HTTP 5xx or timeout
- Block range too large for eth_getLogs returns -32005 limit exceeded error

## How this service works

Ethereum RPC (chain 1): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy calls priced by compute units.

## Output

A standard JSON-RPC 2.0 response object containing either a `result` field with the method's return value (e.g. hex-encoded balance, array of log objects, call return data, trace array) or an `error` field with a code and message describing what went wrong.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nodeflare-ethereum-mainnet-rpc-chain-1-0891cb6e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rpc.nodeflare.app](https://www.zero.xyz/host/rpc.nodeflare.app/llms.txt)