Skip to main content

RPC Endpoint

JSON-RPC and WebSocket Endpoints for 50+ networks

Production RPC Endpoints with global load balancing, rate limit controls, and detailed analytics.

Get Your Free EndpointSee supported networks
Networks
50+
One API key across all of them
Uptime SLA
99.95%
Every tier, including free
Failover
<500ms
Automatic cross-region cutover
Free-tier throughput
40 RPS
Limits per API key, not per IP

What sits between your app and the node

Every call passes the same checks, in this order. You set the key's limits in the dashboard; routing and failover are ours to run.

  1. 01

    Client

    Your app

    Calls one endpoint over JSON-RPC, or holds a WebSocket open for eth_subscribe on newHeads and logs.

  2. 02

    Edge

    Nearest healthy region

    The load balancer picks the closest healthy region in a multi-region footprint. If that region drops, traffic cuts over to another automatically.

    • p99 <100ms
    • Failover <500ms
  3. 03

    Key

    Per-key auth and limits

    The API key is checked before a node sees the call: quotas, rate limits per key rather than per IP, and origin or IP allowlists.

    • Quotas
    • Allowlists
  4. 04

    Nodes

    Shared or dedicated pool

    Same API on both; dedicated endpoints get isolated clusters with no shared neighbours. After a reorg, reads go to nodes on the canonical tip.

    • Shared
    • Dedicated
    • debug_ · trace_ on archive
  5. 05

    Chain

    The network you called

    Any of 50+ networks, mainnet or testnet, behind the same key.

RPC endpoints on 50+ networks

A sample of the networks we serve, from Ethereum and Solana to Cosmos and TON. Pick one for its endpoints and node options.

Celo
Mantle
Tezos
XRP Ledger
Dogecoin
Cardano
See all 50+ networks

Get an API key, then point your client at it

  1. Sign up

    Free tier, no credit card. 600K requests/month included.

  2. Add chains

    Toggle the networks you need, mainnet and testnet, wherever the network runs a public testnet.

  3. Get an API key

    One key works across all chains. Rotate it, or issue one per environment.

  4. Integrate

    Put the RPC Endpoint in your dApp or backend. Works with web3.js, ethers, viem, Anchor, and web3.py.

Set it once in the tools you already use

The endpoint is a provider URL like any other. Put it where your framework expects one and keep the rest of your config.

  • Hardhat

    hardhat.config

  • Foundry

    .env

  • Anchor

    Anchor.toml cluster

  • ethers

    Provider URL

  • viem

    HTTP transport

  • web3.js

    Provider URL

  • web3.py

    HTTPProvider

// ethers v6
import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  process.env.RPC_URL
);

In production, call through your backend so the key stays server-side. For wallets and frontends, set an origin or IP allowlist and a rate limit on the key in the dashboard.

APIs and protections on every key

Wallet & transaction APIs

On supported chains, create wallets, sign transactions, and automate deposits and withdrawals through the same API key.

Data & analytics APIs

Query balances, transaction history, contract state, events, and gas estimates without running your own indexer.

DDoS protection & security

Rate limiting, DDoS mitigation, and API key auth are on for every key by default. Add origin or IP allowlists per key from the dashboard.

What developers ask about the RPC Endpoint

Need something specific? Talk to an engineer.

  • An RPC (Remote Procedure Call) endpoint is a URL your dApp or backend talks to in order to read or write to a blockchain. Instanodes provides managed RPC Endpoints across 50+ networks. You call the URL, we handle the underlying nodes.

  • All standard JSON-RPC methods for each supported chain, plus debug and trace methods on archive tiers. For Ethereum: full `eth_*`, `debug_*`, `trace_*`, and `web3_*` namespaces. For Solana: full JSON-RPC including `getProgramAccounts` and `getSignaturesForAddress`. Chain-specific specs are in our docs.

  • Free tier: 600K requests/month at up to 40 RPS. Paid tiers scale up to enterprise contracts with custom RPS and concurrency. Rate limits apply per API key, not per IP. Share the key safely across your infrastructure.

  • Yes. `eth_subscribe`, `newHeads`, `newPendingTransactions`, and `logs` on EVM chains, plus equivalent subscriptions on Solana, Cosmos, and other networks that support them.

  • Our load balancers detect chain reorgs and route reads to the canonical-tip nodes. For write-after-read consistency, you can pin requests to a single node via the `X-Instanodes-Sticky` header.

  • Yes. Set the Instanodes endpoint as your provider URL in `hardhat.config`, your Foundry `.env`, or your `Anchor.toml` cluster config. Any tool that accepts a JSON-RPC provider URL works the same way.

  • We recommend proxying through your backend for production. For client-side use cases (wallets, frontends), enable per-key allowlists (origin or IP) and rate limits in the dashboard. Free-tier keys can be used client-side for testing.

  • Yes. Dedicated RPC Endpoints get isolated node clusters with no shared neighbors. Available on paid plans, with single-region or multi-region deployment options.

Start sending requests on the free tier

600K requests a month at up to 40 RPS, no credit card. When traffic grows, move to dedicated capacity on the same API.

Get Your Free EndpointSee pricing