Skip to main content
Moving an existing codebase? Migrate with your coding agent: one prompt finds your RPC endpoints and moves the eligible ones behind Boost.
Boost is a drop-in JSON-RPC endpoint. On average, Boost serves 49% of requests, so they never reach your RPC provider. Dollar savings depend on your provider’s pricing; see how to measure it. It is free during early access. Later, you keep most of what Boost saves you. See pricing.

Set up Boost

Connect your provider and send your first request.

See what Boost serves

What Boost serves and what it forwards.

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 blocks, transactions, receipts, and logs 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 for the exact contract.

Is Boost a good fit?

  • Good fit: indexers, explorers, analytics, wallets, and backends that read many blocks, logs, receipts, and transactions.
  • Less savings: apps that mostly send eth_call or other state reads.
To check your own traffic, compare served and forwarded requests in the Boost dashboard. Boost does not replace WebSocket subscriptions. If you want Goldsky to run the provider too, use Edge RPC.

Frequently asked questions

Yes. Boost speaks standard Ethereum JSON-RPC. Change the URL.
No. Send all of them. Boost serves what it can and forwards the rest.
Yes. See tip of chain.
No TTL. Boost serves Goldsky’s indexed chain data, which follows the tip and handles reorgs. pending, safe, finalized, and state reads go to your provider.
Goldsky’s own indexed chain data. Boost never serves another customer’s responses.
Boost forwards it to your provider. It never returns a different result.
Boost is free during early access. Later, you keep most of what Boost saves you. See billing.

Explore Boost

Quickstart

Send a served request and a forwarded one, then update your client.

How it works

Served methods, block tags, batch behavior, and the forwarding contract.

Configure upstreams

Provider connections, custom URLs, credentials, headers, CORS, and timeouts.

Measure results

Read response headers and calculate the share of calls that avoided your provider.

Reference

Endpoint syntax, supported networks, pricing, and limits.

Troubleshooting

Diagnose forwarded reads, 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 for help.