Getting started

Access Ethereum Execution and Consensus RPC endpoints operated by the Node Infrastructure team.

ethnodeops.xyz provides Ethereum RPC access for client developers and researchers. We operate a range of Execution Layer (EL) and Consensus Layer (CL) clients — full and archive nodes — across Mainnet, Sepolia, and Hoodi, and expose them behind clean, load-balanced endpoints.

1. Get an API key

All requests require an API key. To request one, get in touch with the Node Infrastructure team and let us know a little about how you'll use it. We'll reply with your key and the endpoints you need.

Reach out to the Node Infrastructure team:

Message us on Mattermost → Or email node-infrastructure@ethereum.org

When you get in touch, please tell us:

Whether the key is for you as an individual or a shared team key
Your name or team
A short description of your use case

2. Authenticate your requests

There are two ways to pass your key. The header is preferred:

header

X-API-Key: YOUR_API_KEY

If your tooling can't set custom headers, put the key in the URL path, directly after the domain:

url

https://hoodi.rpc.ethnodeops.xyz/YOUR_API_KEY

See Authentication for full details.

3. Make your first request

Fetch the latest block number on Hoodi:

bash

curl https://hoodi.rpc.ethnodeops.xyz \
  -H "X-API-Key: YOUR_API_KEY" \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

You should get back something like:

json

{"jsonrpc":"2.0","id":1,"result":"0x10f2c"}

Where to go next

Endpoints — the full list of Execution and Consensus URLs for every network.
Supported clients — which clients we run and how to target a specific one.
Code examples — curl, ethers.js, web3.py and Beacon REST snippets.