Production decoded-data API vs SQL analytics and the Sim API.
| Dune | GoldRush | |
|---|---|---|
| Wallet data API | Sim API retiring Aug 2026 | Supported |
| Chain coverage (API) | 60+ (Sim) | 100+ chains |
| x402 pay-per-request | None | Native |
Reviewed against Dune's site.
Dune is a SQL-native onchain analytics platform for dashboards and ad-hoc queries across 100+ chains. Its separate Sim API offered a REST wallet-data product, but Dune has announced it is retiring the Sim API on August 1, 2026. GoldRush is a supported, production decoded-data REST API. Use Dune for SQL analytics and dashboards; use GoldRush for decoded wallet, NFT, and pricing data you query from apps and agents.
Production apps and agents that need supported, decoded multichain data over REST, with x402 for autonomous use.
Analysts and data teams who want SQL queries, dashboards, and BI across 100+ chains.
The differences that matter when you ship multichain data, drawn from each product's public docs and pricing.
Dune is retiring its Sim API (the REST wallet/balances/NFT product) on August 1, 2026, with new signups disabled. GoldRush's decoded-data API is a supported, continuing product.
GoldRush returns decoded balances, transactions, NFTs, and prices over REST for production apps. Dune's core strength is SQL analytics and dashboards.
Agents pay per request with no signup or key. Dune has no x402 access to its APIs.
GoldRush serves JSON-RPC on 30+ EVM chains. The Sim API is REST-only with no node service.
What each API covers, row by row. Where a feature exists on both, the note says how they differ.
| Dune | GoldRush | |
|---|---|---|
| Chain coverage | 100+ (SQL), 60+ (Sim API) | 100+ |
| Primary interface | SQL + REST (Sim) | REST |
| Decoded wallet balancesDune via Sim Balances API | Yes | Yes |
| NFT APIDune via Sim Collectibles | Yes | Yes |
| Token prices | Yes | Yes |
| Historical balances at any block | Limited | Yes |
| Onchain analytics | SQL (best in class) | Token + pool prices |
| JSON-RPC included | No | Yes |
| x402 pay-per-request | No | Yes |
| Sim data API status | Retiring Aug 1, 2026 | n/a |
Sources: GoldRush docs and Dune.
Plans as each provider lists them, reviewed . Check Dune for current rates.
Get all token balances for a wallet on Ethereum. Compare the request shape and how much each call returns.
// Dune Sim API: wallet balances (Sim API retires Aug 1, 2026)
const res = await fetch(
"https://api.sim.dune.com/v1/evm/balances/" +
"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?chain_ids=1",
{ headers: { "X-Sim-Api-Key": process.env.SIM_API_KEY } }
);
const { balances } = await res.json();// GoldRush, wallet balances on any chain
const res = await fetch(
"https://api.covalenthq.com/v1/eth-mainnet/" +
"address/vitalik.eth/balances_v2/",
{ headers: { Authorization: "Bearer " + process.env.GOLDRUSH_API_KEY } }
);
const { data } = await res.json();
console.log(data.items);The migration guide maps Dune endpoints to GoldRush one by one, including the ones GoldRush doesn't replace, with code you can paste.
Decoded multichain data API vs JSON-RPC and node infrastructure.
Multichain data API with x402 vs Web3 API with auth and Streams.
Decoded multichain data API vs RPC infrastructure with marketplace add-ons.
Decoded multichain data vs Ethereum-first JSON-RPC infrastructure.
Decoded multichain data API vs decentralized RPC with Advanced APIs.
Foundational multichain data API vs GraphQL-first onchain query platform.
API-first decoded data vs decentralized subgraph indexing.
Self-serve decoded-data API vs enterprise data infrastructure.
Turnkey decoded-data API vs subgraph indexing and streaming pipelines.
Onchain wallet and decoded data vs market and price data.
Decoded data across 100+ chains vs wallet and portfolio API.