GoldRush JSON-RPC
Multi-chain JSON-RPC service backed by an analytics-driven router that scores every(provider, chain, endpoint) triple by success rate, p50/p95 latency, error class, and cost, and dispatches each call to whichever upstream is currently winning that route.
- Endpoint:
https://rpc.goldrushdata.com/v1/{chain}(HTTP);wss://rpc.goldrushdata.com/v1/{chain}(Solana subscriptions) - Pricing: pay-per-call from your GoldRush credit balance
- EVM namespaces:
eth_*,net_*,web3_*,debug_*,trace_* - Solana: full account/block/transaction/token/slot/network/inflation method set + WebSocket subscriptions
- Depth: full archive (per-chain coverage varies for
debug_*/trace_*) - SLA: 99.9% monthly uptime for production accounts
Authorization: Bearer <key> HTTP header, so keys never appear in URLs.
Header-based auth pattern
Launch chains
Solana uses the Solana JSON-RPC method set (not
eth_*), over HTTP and over WebSocket (wss://rpc.goldrushdata.com/v1/solana-mainnet) for subscriptions. With @solana/kit: createSolanaRpcFromTransport(createDefaultRpcTransport({ url, headers: { Authorization: \Bearer {key}\` } }))`. With `@solana/web3.js`: `new Connection(url, { httpHeaders: { Authorization: \`Bearer ` } })`.
Product decision matrix
Cross-reference
JSON-RPC is the lowest-level GoldRush product. For most application-level needs (wallet UIs, dashboards, agents), one of the higher-level products is a better fit. JSON-RPC is the right choice when you need primitives, i.e. when the response of aFoundational API call would already be one round-trip too many.