Covalent

Covalent’s GoldRush is a managed blockchain-data platform that turns chain activity into provider-maintained API responses. Its Foundational API is aimed at applications that need decoded, typed, and enriched blockchain data without building a separate indexer for every supported chain.

Prebuilt data for wallets, portfolios, and transaction history

The Foundational API can return wallet balances, token transfers, transactions, token and NFT data, logs, prices, and contract-related information across many chains. Responses can include decoded event logs, token metadata, scaled amounts, and USD pricing, reducing repeated client-side parsing for portfolio, accounting, and dashboard products.

Its common data layer covers native balances, ERC-20, ERC-721, and ERC-1155 assets, allowances, blocks, historical transactions, gas summaries, NFT ownership, token holders, and prices. Custom endpoints can provide direct SQL access for saved queries when a standard endpoint does not fit a needed dataset.

REST for enriched data and RPC for raw calls

Foundational API uses HTTP REST endpoints and SDKs: the caller chooses a documented chain and endpoint rather than declaring a new response schema in each request. GoldRush also offers JSON-RPC for raw EVM methods and supported Solana JSON-RPC and WebSocket subscriptions, leaving decoding and request composition closer to the application.

Coverage is broad but not uniform. Some enrichments, including internal transactions and historical-balance retrieval, are restricted to designated Foundational Chains. A broad network count therefore cannot replace checking whether the required endpoint, depth, and enrichment are available on the target chain.

A standardized counterpart to custom Subgraphs

Covalent fits wallets, portfolio trackers, tax and accounting products, DeFi dashboards, and agents that need a maintained multichain response model. Its API key is shared across GoldRush products, while request capacity and monthly credits need to match the endpoint mix and traffic pattern.

The Graph is the close alternative when a team needs a protocol-specific GraphQL schema and bespoke event-to-entity transformations. Covalent is more direct when the requirement fits a maintained REST data product; a custom index is more flexible for unique protocol metrics or relationships that the provider model does not expose.