> ## Documentation Index > Fetch the complete documentation index at: https://docs.goldsky.com/llms.txt > Use this file to discover all available pages before exploring further. # How Boost routes requests > Learn which JSON-RPC requests Boost can serve, which calls always forward, and how mixed batches are handled. export const BoostDiagram = () =>
How Boost routes JSON-RPC requests Requests travel from your application to Boost. Eligible historical reads are answered from Goldsky indexed data. Other calls are forwarded to your RPC provider. Your app JSON-RPC Boost eligible read Goldsky data served by Boost everything else Your provider forwarded by Boost How Boost routes JSON-RPC requests Requests travel from your application to Boost. Eligible historical reads are answered from Goldsky indexed data. Other calls are forwarded to your RPC provider. Your app JSON-RPC Boost eligible read Goldsky data served by Boost other calls Your provider forwarded The response returns through the same Boost URL.
; Boost reads the JSON-RPC method and parameters, then chooses the response source. The API key identifies your project's Boost; that project's network configuration supplies the upstream for calls that need your provider. ## Routing model | Request | Route | Response headers | | ------------------------------------------------------------- | ------------- | ------------------------------------------ | | Eligible historical read that Goldsky can answer | CDN | `x-cache: HIT`, `x-edge-source: cache` | | `eth_chainId` or `net_version` | Boost | `x-edge-source: static` | | Eligible read whose data is not available | Your upstream | `x-cache: MISS`, `x-edge-source: endpoint` | | Tagged block, write, trace, state read, or unsupported method | Your upstream | `x-cache: MISS`, `x-edge-source: endpoint` | A failed or incomplete cache lookup falls back to your upstream. A cache miss can add proxy latency, but it does not substitute a different historical result. ## Methods eligible for indexed data | Method | Eligible when | | --------------------------- | --------------------------------------------------------------------------------- | | `eth_getBlockByNumber` | The block is a concrete hexadecimal height | | `eth_getBlockByHash` | The requested block is available in Goldsky's indexed data | | `eth_getTransactionByHash` | The requested transaction is available in Goldsky's indexed data | | `eth_getTransactionReceipt` | The requested receipt is available in Goldsky's indexed data | | `eth_getLogs` | `fromBlock` and `toBlock` are concrete hexadecimal heights, or `blockHash` is set | | `eth_getBlockReceipts` | The block is a concrete hexadecimal height | Eligibility does not guarantee a hit. If Goldsky does not have the requested data, Boost forwards the request. ## Block tags always forward Requests using `latest`, `pending`, `safe`, `finalized`, or `earliest` are always forwarded. The same rule applies to `eth_getLogs` when either range bound is a tag. Your upstream is the authority on the chain head. Serving a tag from indexed data could otherwise return a block behind your provider or a block affected by a reorganization. Use a concrete hexadecimal height when you want an eligible historical read. ## Everything else forwards Writes, traces, and state reads such as `eth_call` and `eth_getBalance` go to your configured upstream. Boost also forwards methods it does not recognize as eligible. For a forwarded call, Boost preserves the JSON-RPC method, parameters, and ID. The result body comes from your upstream. HTTP headers are handled separately; see [request and response forwarding](/boost/configuration#request-and-response-forwarding). ## Batch requests Boost evaluates JSON-RPC batches per item. Eligible items can come from Goldsky data while the remaining items are sent to your upstream together in one onward batch. * Give every item a unique `id`. JSON-RPC does not guarantee response order, so match results by ID. * Use `x-edge-billable` as the served-item count. `x-cache` is `HIT` only when Boost serves every item in the batch. * Keep arrays at 100 items or fewer. Larger arrays are forwarded whole without cache lookups. For example, a batch where Boost serves 44 of 45 items reports `x-cache: MISS` and `x-edge-billable: 44`. ## Authentication and endpoint selection The endpoint format is: ```text theme={"dark"} https://edge.goldsky.com/boost/{chain}?key={your-api-key} ``` The chain path selects the network. The Goldsky key identifies your project's Boost, and that network's configuration selects the active upstream. Your provider URL and persistent provider credentials stay in the configuration rather than traveling in each request. ## Related topics - [Measure Boost traffic](/boost/observability.md) - [Cut RPC costs with Boost](/boost.md) - [Troubleshoot Boost](/boost/troubleshooting.md) - [Boost reference](/boost/reference.md) - [Configure Boost upstreams](/boost/configuration.md)