Decoded multichain data API vs JSON-RPC and node infrastructure.
| Alchemy | GoldRush | |
|---|---|---|
| Chain coverage | 75+ | 100+ chains |
| Decoded data + JSON-RPC | Separate products | One API |
| Pricing model | Compute units | Flat credits |
Reviewed against Alchemy's site.
GoldRush is a decoded, multichain data API. One call returns wallet balances, transactions with parsed logs, NFTs with metadata, and prices. Alchemy is a node-infrastructure provider, with NFT and Enhanced APIs layered on top of its JSON-RPC product. If your app is wallets, portfolio trackers, tax tools, or agentic workflows that need ready-to-consume data across many chains, GoldRush is the shorter path. If you primarily need high-throughput JSON-RPC plus Alchemy-specific products like Account Kit, Alchemy is the safer pick.
Apps that need decoded, multichain wallet, NFT, and pricing data without writing per-chain indexers. Autonomous AI agents that pay per request via x402.
Apps centered on high-throughput JSON-RPC, Alchemy's Enhanced APIs, and Account Kit for embedded wallets.
The differences that matter when you ship multichain data, drawn from each product's public docs and pricing.
Balances, transactions, NFTs, and prices return from a single GoldRush endpoint. On Alchemy these live across separate Token, NFT, Prices, and Portfolio APIs.
Spot prices for DEX pools ship natively alongside spot and historical token prices, plus OHLCV candles for Hyperliquid markets.
One credit unit across every endpoint, instead of per-method compute-unit metering that varies by call.
Consistent decoded wallet, NFT, and pricing primitives across 100+ chains from one product.
What each API covers, row by row. Where a feature exists on both, the note says how they differ.
| Alchemy | GoldRush | |
|---|---|---|
| Chain coverageAlchemy lists 75 supported blockchains | 75+ | 100+ |
| JSON-RPC endpoints | All supported chains | 30+ EVM chains |
| Decoded wallet balances APIBoth expose token balances | Yes | Yes |
| Token pricesAlchemy ships a Prices API | Yes | Yes |
| DEX pool spot pricesBeyond Alchemy's spot/historical token prices | No | Yes |
| OHLCV candles | No | Hyperliquid only |
| Historical balances at any block | Limited | Yes |
| x402 pay-per-requestAlchemy ships x402 via AgentPay | Yes | Yes |
| 14-day trial | Free tier with compute units | 25k credits |
| Hyperliquid endpoints | No | Yes |
| Bitcoin support | No | Yes |
Sources: GoldRush docs and Alchemy.
Plans as each provider lists them, reviewed . Check Alchemy for current rates.
Get all ERC-20 balances for a wallet on Ethereum mainnet. Compare the request shape and how much each call returns.
// Alchemy: getTokenBalances, then getTokenMetadata per token
import { Alchemy, Network } from "alchemy-sdk";
const alchemy = new Alchemy({
apiKey: process.env.ALCHEMY_API_KEY,
network: Network.ETH_MAINNET,
});
const balances = await alchemy.core.getTokenBalances(
"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
);
// Each balance still needs metadata to be useful.
// Resolve symbol, decimals, and price separately.
const enriched = await Promise.all(
balances.tokenBalances.map(async (b) => {
const meta = await alchemy.core.getTokenMetadata(b.contractAddress);
return { ...b, ...meta };
})
);// 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 Alchemy endpoints to GoldRush one by one, including the ones GoldRush doesn't replace, with code you can paste.
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.
Production decoded-data API vs SQL analytics and the Sim API.
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.