Skip to main content

Documentation Index

Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

GoldRush JSON-RPC is pay-per-call from your GoldRush credit balance. The same credits work across every GoldRush product.

​
Rates

Each method is priced in credits per call.
TierRateMethods
Standard0.01 creditsAll eth_*, net_*, and web3_* methods.
Trace0.015 creditsDebug and trace methods (see below).

​
Trace-tier methods

The following methods are charged at 0.015 credits per call because they replay execution against archive state:
  • debug_traceTransaction
  • debug_traceCall
  • debug_traceBlockByNumber
  • debug_traceBlockByHash
  • trace_block
  • trace_transaction
  • trace_filter
  • trace_call

​
How to estimate cost

A typical wallet that polls eth_blockNumber once per second and eth_getBalance once per minute uses: 
eth_blockNumber:  0.01 × 60 × 60 × 24 = 864.0 / day
eth_getBalance:   0.01 × 60 × 24      =  14.4 / day
                                       ────────
                                       ~880 credits / day
A block-explorer indexer that calls debug_traceBlockByNumber once per finalized block on Ethereum (~12s blocks): 
debug_traceBlockByNumber: 0.015 × 7,200 blocks/day = 108 credits / day

​
What counts as a call

  • Each request in a JSON-RPC batch counts separately. A batch of 10 eth_getBalance calls costs 0.1 credits.
  • Failed requests caused by user error (-32600, -32602) are not charged. Failures inside the upstream node (e.g. revert in eth_call) are charged, since the node did the work.
  • Cached responses are charged at the standard rate. Edge caching reduces latency, not cost.

Endpoint details

Production endpoint with archive, debug, trace.

Supported chains

Each chain’s method catalog, grouped by category.