Skip to main content
GoldRush JSON-RPC gives you raw, uniform JSON-RPC access to every chain GoldRush supports: EVM chains and Solana. On EVM chains it is drop-in compatible with viem, ethers, web3.js, and web3.py, with archive depth, debug_*, and trace_*. On Solana it speaks the full Solana JSON-RPC and WebSocket subscription protocol, drop-in compatible with @solana/kit, @solana/web3.js, and solana-py.
GoldRush JSON-RPC uses the same API key as your other GoldRush products. No new account, no second dashboard.

​
What is GoldRush JSON-RPC?

A JSON-RPC interface in front of a smart router that fronts multiple independent upstream providers. GoldRush continuously collects analytics per (provider, chain, method) triple, including success rate, p50/p95 latency, error class, and cost. Each incoming call is routed to the provider that currently scores best on the cost/performance frontier for that chain and method. Failed providers are demoted automatically and re-probed on a backoff. 
                       ╔═ GoldRush Edge ════╗
                       ║                    ║░            ╔═════════════════╗
╔══════════╗           ║   ╔══════════════╗ ║░            ║ Best upstream   ║░
║ Your App ║░ ──API──▶ ║   ║ Smart Router ║ ║░ ──route──▶ ║ provider for    ║░
╚══════════╝░          ║   ╚══════════════╝ ║░            ║ (chain, method) ║░
 ░░░░░░░░░░░░          ║                    ║░            ╚═════════════════╝░
                       ╚════════════════════╝░             ░░░░░░░░░░░░░░░░░░░
                        ░░░░░░░░░░░░░░░░░░░░░░
The result: lower p99 latency than any single provider, no single-vendor dependency, and a uniform error surface across chains and node software.

​
What you get

  • Pay-per-call from your GoldRush credits
  • Archive depth (full historical state)
  • debug_* and trace_* namespaces
  • Sub-100ms p50 latency from regional edge POPs
  • 99.9% production SLA
  • Suited for explorers, indexers, wallets, and production apps

​
What’s supported

  • 10 mainnet networks at launch: Ethereum, Polygon, BNB Smart Chain, Arbitrum, Base, HyperEVM, MegaETH, Monad, Tempo, and Solana
  • EVM methods across the eth_*, net_*, web3_*, debug_*, and trace_* namespaces
  • Solana methods: the full account, block, transaction, token, slot, network, and inflation method set, plus WebSocket subscriptions (accountSubscribe, logsSubscribe, programSubscribe, signatureSubscribe, …)
  • Drop-in compatibility with viem, ethers, web3.js, web3.py (EVM) and @solana/kit, @solana/web3.js, solana-py (Solana), plus raw fetch and curl
  • Header-based authentication so your API key never appears in URLs, server logs, or copy-pasted endpoints
See supported chains for the full chain list. Each chain page enumerates its methods by category in the sidebar.

​
JSON-RPC vs Foundational API

JSON-RPC

Raw, untyped, opcode-level access. You compose calls. Best for: building wallets, indexers, simulators, and anything that needs the lowest level of node access.

Foundational API

Decoded, typed, multi-chain REST endpoints (token balances, NFT metadata, USD pricing, transaction histories). Best for: dashboards, agents, anything that consumes already-enriched data.
The two products use the same API key. Use them together: JSON-RPC for primitives, Foundational API for the heavy lifting.

​
Next steps

Quickstart

Make your first call in under a minute.

Authentication

How to attach your API key to requests.

Supported chains

Which networks are live.

Migrating from another provider

Side-by-side diffs against Infura, Alchemy, and Ankr.