BNB Smart Chain RPC, on the same interface as every other chain.
Iteradian provides a managed BNB Smart Chain RPC endpoint. It accepts standard eth_* JSON-RPC 2.0 calls, including batch requests, and routes them across a pool of managed BNB Smart Chain nodes with an enforced rate limit, fall-forward failover and per-request usage analytics.
POST https://api.iteradian.com/rpc/v1/bsc-mainnet
- Slug
- bsc-mainnet
- Aliases
- bsc-mainnet, bnb-mainnet
- Status
- No healthy node right now — see status
- Verified
Why use a managed BNB Smart Chain endpoint?
BNB Smart Chain is EVM-compatible with short block times, which makes it unusually punishing for polling-based integrations. Iteradian shows average and P95 latency for your own traffic, so you can tell the difference between your poll loop being slow and the chain being slow.
How do I connect to BNB Smart Chain?
- 01
Create an API key
Sign up for Iteradian and create a key in the dashboard. Production keys are prefixed
itrd_live_and test keysitrd_test_. The plaintext key is shown exactly once, so store it in a secret manager — never in source control. - 02
Send a JSON-RPC 2.0 request
cURL curl -X POST https://api.iteradian.com/rpc/v1/bsc-mainnet \ -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/bsc-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();Python import os, requests res = requests.post( "https://api.iteradian.com/rpc/v1/bsc-mainnet", headers={"X-Api-Key": os.environ["ITERADIAN_API_KEY"]}, json={"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []}, ) print(res.json()["result"]) - 03
Handle throttling
Requests past your plan’s per-second rate or concurrency ceiling return HTTP 429 with JSON-RPC error code
-32005and aretryAftervalue inerror.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.
Common BNB Smart Chain RPC methods
| Method | Description |
|---|---|
| eth_blockNumber | Returns the number of the most recent block. |
| eth_getBalance | Returns the balance of an account at a given block. |
| eth_call | Executes a call immediately without creating a transaction. |
| eth_getLogs | Returns logs matching a filter — the basis of most indexers. |
| eth_getTransactionReceipt | Returns the receipt of a transaction by hash. |
| eth_sendRawTransaction | Submits a signed transaction to the network. |
BNB Smart Chain RPC pricing
| Plan | Price | Included |
|---|---|---|
| Free RPC | $0/mo | 25 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/mo | 250 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/mo | 500 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 RPC | Custom | Custom requests per second · Custom concurrent connections · Unlimited monthly requests · Unlimited API keys · Dedicated infrastructure |
BNB Smart Chain RPC FAQ
01How do I get a BNB Smart Chain RPC endpoint?
Create an Iteradian account, generate an API key, and send JSON-RPC 2.0 requests to https://api.iteradian.com/rpc/v1/bsc-mainnet with the key in an X-Api-Key header (Authorization: Bearer also works). New organizations start with a 7-day free trial.
02What happens if I exceed the BNB Smart Chain 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.
03What happens if a BNB Smart Chain node goes down?
The gateway fails a request over to another healthy BNB Smart Chain 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.
04Which BNB Smart Chain JSON-RPC methods are supported?
BNB Smart Chain 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/bsc-mainnet with the same API key.