> ## 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. # Cut RPC costs with Boost > Keep your current RPC provider while Boost serves historical and tip-of-chain reads from Goldsky's indexed data and forwards everything else upstream. export const BoostDiagram = () =>
How Boost routes JSON-RPC requests Requests travel from your application to Boost. Eligible historical and tip-of-chain 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 and tip-of-chain 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.
; export const BoostAgentActions = () => { const prompt = `Help me add Goldsky Boost to an existing EVM app. Use the current documentation at https://docs.goldsky.com/boost and confirm the cached methods and supported networks before changing code. Ask which RPC client and provider I use, then show the smallest endpoint change and how to verify cache hits with x-cache and x-edge-billable.`; const encoded = encodeURIComponent(prompt); const actionStyle = { display: 'inline-flex', alignItems: 'center', justifyContent: 'center', gap: 8, flex: '0 0 auto', height: 38, boxSizing: 'border-box', padding: '0 12px', borderRadius: 10, border: '1px solid var(--gsk-edge, rgba(17,24,39,0.2))', background: 'transparent', color: 'var(--gsk-ink, #111827)', fontSize: 13, fontWeight: 600, lineHeight: 1, whiteSpace: 'nowrap', textDecoration: 'none', cursor: 'pointer', transition: 'border-color 150ms ease, background-color 150ms ease, transform 150ms ease' }; return <>
Use your AI assistant
Start from a prompt tailored to your existing EVM client.
ChatGPT Claude
; }; Boost reduces the traffic sent to an RPC provider you already use. Historical and tip-of-chain reads come from Goldsky's indexed data. Every other JSON-RPC call forwards to your configured endpoint. Your application keeps one RPC interface and one response shape. You keep control of the upstream provider, while repeatable reads can avoid reaching it at all. Configure an upstream and verify your first cache hit. Understand cache eligibility, block tags, batches, and forwarding. ## How Boost fits into your stack 1. Your application sends JSON-RPC requests to a Boost URL instead of directly to your provider. 2. Boost serves eligible reads when Goldsky has the requested data, from any historical block up to the chain tip. 3. Calls Boost cannot serve are forwarded to the active upstream configured for that network. The routing decision uses the request method and parameters. It does not require an additional request to your provider. Boost preserves the JSON-RPC interface, but it is still an HTTP proxy. It normalizes some transport headers and manages CORS at the edge. See [request and response forwarding](/boost/configuration#request-and-response-forwarding) for the exact contract. ## Use Boost when * You want to keep your current provider and client libraries. * Your workload reads blocks, transactions, receipts, or log ranges, at fixed heights or at the latest block. * You want to reduce upstream request volume without changing application behavior on a cache miss. * You need to measure which requests Boost served and which reached your provider. Boost is not a replacement for WebSocket subscriptions. State reads such as `eth_call` and `eth_getBalance`, and the `pending`, `safe`, and `finalized` tags, remain with your provider. If you want Goldsky to operate the RPC provider layer as well, use [Edge RPC](/edge-rpc/introduction). ## Explore Boost Make a cache hit, compare a forwarded request, and update an existing client. Cached methods, block tags, batch behavior, and the forwarding contract. Provider connections, custom URLs, credentials, headers, CORS, and timeouts. Read response headers and calculate the share of calls that avoided your provider. Endpoint syntax, supported networks, billing, and limits. Diagnose misses, provider errors, CORS, large batches, and verification issues. ## Getting help Can't find what you're looking for? Reach out to us at [support@goldsky.com](mailto:support@goldsky.com) for help. ## Related topics - [Pricing: plans, metering, and product costs](/pricing/summary.md) - [How Boost routes requests](/boost/how-it-works.md) - [Boost reference](/boost/reference.md) - [Configure Boost upstreams](/boost/configuration.md) - [Troubleshoot Boost](/boost/troubleshooting.md)