Avalanche RPC, on the same interface as every other chain.

The Avalanche C-Chain is the EVM-compatible chain in the Avalanche primary network, so it speaks the same eth_* JSON-RPC dialect as Ethereum. Iteradian routes C-Chain traffic through the same key, the same enforced limits and the same analytics as your other networks.

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 -X POST https://api.iteradian.com/rpc/v1/avalanche-mainnet \
     -H "Content-Type: application/json" \
     -H "X-Api-Key: itrd_live_YOUR_KEY" \
     -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

   const res = await fetch("https://api.iteradian.com/rpc/v1/avalanche-mainnet", {
     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();

   import os, requests
   
   res = requests.post(
       "https://api.iteradian.com/rpc/v1/avalanche-mainnet",
       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.

Related networks