Ethereum Sepolia RPC, on the same interface as every other chain.

Iteradian provides a managed Ethereum Sepolia testnet RPC endpoint. Sepolia is the recommended Ethereum test network for application developers, and it is included in every Iteradian plan at no extra cost.

Endpoint

POST https://api.iteradian.com/rpc/v1/eth-testnet

Slug
eth-testnet
Aliases
eth-testnet, eth-sepolia, ethereum-sepolia
Status
No healthy node right now — see status
Verified
01

Why use a managed Ethereum Sepolia endpoint?

Sepolia is the standard Ethereum test network for application development. Use a separate API key for test work and its traffic stays in that key's own usage series, apart from your production key.

02

How do I connect to Ethereum Sepolia?

  1. 01

    Create an API key

    Sign up for Iteradian and create a key in the dashboard. Production keys are prefixed itrd_live_ and test keys itrd_test_. The plaintext key is shown exactly once, so store it in a secret manager — never in source control.

  2. 02

    Send a JSON-RPC 2.0 request

    cURL
    curl -X POST https://api.iteradian.com/rpc/v1/eth-testnet \
      -H "Content-Type: application/json" \
      -H "X-Api-Key: itrd_live_YOUR_KEY" \
      -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
    TypeScript
    const res = await fetch("https://api.iteradian.com/rpc/v1/eth-testnet", {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        "X-Api-Key": process.env.ITERADIAN_API_KEY!,
      },
      body: JSON.stringify({
        jsonrpc: "2.0",
        id: 1,
        method: "eth_blockNumber",
        params: [],
      }),
    });
    
    const { result } = await res.json();
    Python
    import os, requests
    
    res = requests.post(
        "https://api.iteradian.com/rpc/v1/eth-testnet",
        headers={"X-Api-Key": os.environ["ITERADIAN_API_KEY"]},
        json={"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []},
    )
    
    print(res.json()["result"])
  3. 03

    Handle throttling

    Requests past your plan’s per-second rate or concurrency ceiling return HTTP 429 with JSON-RPC error code -32005 and a retryAfter value in error.data. Past the monthly allowance, requests run as metered overage until the plan’s overage cap, then return 429 with -32007. Throttled requests are recorded in your usage and request log too — nothing is dropped silently.

03

Common Ethereum Sepolia RPC methods

Commonly used Ethereum Sepolia JSON-RPC methods
MethodDescription
eth_blockNumberReturns the number of the most recent block.
eth_getBalanceReturns the balance of an account at a given block.
eth_callExecutes a call immediately without creating a transaction.
eth_getLogsReturns logs matching a filter — the basis of most indexers.
eth_getTransactionReceiptReturns the receipt of a transaction by hash.
eth_sendRawTransactionSubmits a signed transaction to the network.
04

Ethereum Sepolia RPC pricing

Ethereum Sepolia is included in every plan
PlanPriceIncluded
Free RPC$0/mo25 requests per second · 10 concurrent connections · 3,000,000 requests per month included · 3 API keys · Hard cap at the monthly allowance, no overage billed
Developer RPC$39/mo250 requests per second · 100 concurrent connections · 25,000,000 requests per month included · 10 API keys · Overage $0.005 per 1,000 requests, capped at $150 per billing period
Professional RPC$169/mo500 requests per second · 500 concurrent connections · 80,000,000 requests per month included · 25 API keys · Overage $0.003 per 1,000 requests, capped at $350 per billing period
Dedicated RPCCustomCustom requests per second · Custom concurrent connections · Unlimited monthly requests · Unlimited API keys · Dedicated infrastructure
05

Ethereum Sepolia RPC FAQ

01

How do I get a Ethereum Sepolia RPC endpoint?

Create an Iteradian account, generate an API key, and send JSON-RPC 2.0 requests to https://api.iteradian.com/rpc/v1/eth-testnet with the key in an X-Api-Key header (Authorization: Bearer also works). New organizations start with a 7-day free trial.

02

What happens if I exceed the Ethereum Sepolia rate limit?

The request receives HTTP 429 with a JSON-RPC error body. Code -32005 means your organization's per-second rate or concurrency limit — retry after `error.data.retryAfter` seconds. Code -32006 means the monthly quota is used up (`error.data.resetsAt` says when it resets) and -32007 means the overage spend cap is reached; retrying either cannot succeed until the period resets or the plan changes. Limits are shared by all of the organization's keys.

03

What happens if a Ethereum Sepolia node goes down?

The gateway fails a request over to another healthy Ethereum Sepolia node automatically, across up to 3 nodes. Transaction submissions are sent to one node and never retried or replayed by the gateway, so it cannot broadcast a transaction twice. If every node fails, the response is HTTP 503.

04

Which Ethereum Sepolia JSON-RPC methods are supported?

Ethereum Sepolia is EVM-compatible, so the standard eth_* JSON-RPC methods are forwarded to the node, including batch requests (a batch of N calls counts as N requests). Whether trace_*, debug_* or archive queries work depends on the node, so they are not guaranteed. For eth_subscribe, open the WebSocket endpoint wss://rpc.iteradian.com/ws/v1/eth-testnet with the same API key.

Related networks

Start

Point one endpoint at Iteradian and watch where the traffic goes.

Create a key, send a JSON-RPC call, and read that request back in your analytics a second later. No migration, no contract.

Trial
7 days, no card required
Setup
One endpoint, one header
Commitment
Monthly or annual, cancel any time