> ## 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.

# Pricing

> Per-method credit rates for GoldRush JSON-RPC.

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**.

| Tier         |              Rate | Methods                                     |
| ------------ | ----------------: | ------------------------------------------- |
| **Standard** |  **0.01 credits** | All `eth_*`, `net_*`, and `web3_*` methods. |
| **Trace**    | **0.015 credits** | Debug 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`
* `trace_callMany`
* `trace_rawTransaction`
* `trace_replayBlockTransactions`
* `trace_replayTransaction`
* `trace_get`

## Solana rates

GoldRush routes Solana through a multi-provider backend (an RPC aggregator that fronts dRPC and others), which classifies every method as **light** or **heavy**. We mirror that split, so two tiers cover every Solana method:

| Tier      |             Rate | Methods                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| --------- | ---------------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Light** | **0.01 credits** | Single-object reads and writes, and all subscriptions: `getAccountInfo`, `getBalance`, `getSlot`, `getBlockHeight`, `getLatestBlockhash`, `getTransaction`, `sendTransaction`, `simulateTransaction`, `getSignatureStatuses`, `getHealth`, `getVersion`, `getEpochInfo`, `getTokenAccountBalance`, `getTokenSupply`, and the WebSocket subscriptions (`accountSubscribe`, `logsSubscribe`, `signatureSubscribe`, …), billed per delivered notification.                                        |
| **Heavy** | **0.05 credits** | Unbounded account/program scans, block bodies, and signature/range history: `getProgramAccounts`, `getBlock`, `getBlocks`, `getBlocksWithLimit`, `getBlockProduction`, `getMultipleAccounts`, `getLargestAccounts`, `getVoteAccounts`, `getSignaturesForAddress`, `getTokenAccountsByOwner`, `getTokenAccountsByDelegate`, `getTokenLargestAccounts`, `getInflationReward`, `getSupply`, `getLeaderSchedule`, `getRecentPerformanceSamples` (plus the deprecated `getConfirmed*` equivalents). |

Opening or closing a subscription is free; you are billed only for notifications delivered.

<Note>
  `getProgramAccounts` and `programSubscribe` can return large result sets. Always scope them with `filters` (`dataSize`, `memcmp`) and `dataSlice` to keep both responses and your credit usage small.
</Note>

## 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.

<CardGroup cols={2}>
  <Card title="Endpoint details" href="/goldrush-json-rpc/edge-tier" icon="bolt">
    Production endpoint with archive, debug, trace.
  </Card>

  <Card title="Supported chains" href="/goldrush-json-rpc/supported-chains" icon="link">
    Each chain's method catalog, grouped by category.
  </Card>
</CardGroup>