Covalenthq GoldRush Multichain Data APIs

Name: GoldRush Multichain Data APIs
Brand: GoldRush Multichain Data APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer37 EndpointsREST

For Agents

Pull token balances, portfolios, transfers, NFTs, logs, and address activity across many EVM chains and Bitcoin from one bearer-authenticated REST API.

Use for: I need to fetch the token balances for a wallet on Ethereum, Get the historical portfolio value of a wallet over the last 30 days, List all ERC-20 transfers for a specific wallet on Polygon, Find the NFTs owned by a wallet across supported chains

Not supported: Does not broadcast transactions, run smart contract code, or provide custodial wallet services - use for read-only multichain data lookups only.

Jentic publishes the only available OpenAPI specification for GoldRush Multichain Data APIs, keeping it validated and agent-ready. Covalent's GoldRush Multichain Data APIs expose unified blockchain data across 37 endpoints, covering token balances, historical portfolios, ERC-20 transfers, NFT ownership, log events by address or topic, block lookups, gas prices, address activity across chains, and Bitcoin HD wallet balances. Authentication is via a bearer GoldRush API key. Suitable for crypto wallet apps, multichain analytics dashboards, NFT explorers, and AI agents that need consistent JSON over dozens of chains without writing a different RPC client per chain.

Install Jentic One Beta

Connect the GoldRush Multichain Data APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoldRush Multichain Data APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcovalenthq.com%2Fcovalent-goldrush-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcovalenthq.com%2Fcovalent-goldrush-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GoldRush Multichain Data APIs.

Fetch token, native, and historical balances for a wallet on any supported chain

Retrieve historical portfolio value over time for a wallet

List ERC-20 transfers and outstanding token approvals for a wallet

Look up NFT holdings and verify ownership of a specific collection or token ID

GET STARTED

Start building with GoldRush Multichain Data APIs

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GoldRush Multichain Data APIs for, with concrete tasks.

★ Crypto Wallet Dashboard

Power a multichain wallet view that shows token balances, NFT holdings, and historical portfolio value for a connected address. GET /v1/{chainName}/address/{walletAddress}/balances_v2/ returns ERC-20 and native balances per chain, /portfolio_v2/ returns the historical curve, and /balances_nft/ returns the NFT holdings. One API key, dozens of chains, consistent JSON shape.

Call GET /v1/{chainName}/address/{walletAddress}/balances_v2/ for each chain the user holds assets on, then GET /v1/{chainName}/address/{walletAddress}/portfolio_v2/ for the historical chart

NFT Ownership Gating

Verify whether a wallet owns a specific NFT collection or token before granting access to a gated experience. GET /v1/{chainName}/address/{walletAddress}/collection/{collectionContract}/ confirms collection ownership, and the per-token variant verifies a specific token ID. Suitable for token-gated content, Discord bots, and event ticketing.

Call GET /v1/{chainName}/address/{walletAddress}/collection/{collectionContract}/token/{tokenId}/ to confirm the wallet holds the specific token before granting access

On-Chain Event Indexing

Index log events by contract address or topic hash to feed analytics, alerting, or compliance pipelines without running a node. GET /v1/{chainName}/events/address/{contractAddress}/ returns logs for a contract, and /events/topics/{topicHash}/ filters by event signature. Useful for protocol teams that need a unified event feed across chains.

Poll GET /v1/{chainName}/events/topics/{topicHash}/ every minute and write each new log to a Kafka topic

AI Agent Crypto Assistant

Let an AI agent answer wallet and on-chain questions like 'what is wallet X holding on Polygon' through Jentic. The agent searches by intent, executes the matching GoldRush operation, and the bearer GoldRush API key stays in the encrypted vault. Cuts the typical multi-day RPC integration down to minutes.

Use Jentic to search 'get token balances for a wallet', load the schema for GET /v1/{chainName}/address/{walletAddress}/balances_v2/, and execute it with the user-supplied chain and address

Key Endpoints

37 endpoints — jentic publishes the only available openapi specification for goldrush multichain data apis, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/{chainName}/address/{walletAddress}/balances_v2/

Token balances for a wallet

GET

/v1/{chainName}/address/{walletAddress}/portfolio_v2/

Historical portfolio for a wallet

GET

/v1/{chainName}/address/{walletAddress}/transfers_v2/

ERC-20 transfers for a wallet

GET

/v1/{chainName}/address/{walletAddress}/balances_nft/

NFT holdings for a wallet

GET

/v1/{chainName}/events/address/{contractAddress}/

Log events by contract address

GET

/v1/{chainName}/events/topics/{topicHash}/

Log events by topic hash

GET

/v1/chains/

List supported chains

GET

/v1/{chainName}/event/{eventType}/gas_prices/

Gas prices for an event type

GET

/v1/{chainName}/address/{walletAddress}/balances_v2/

Token balances for a wallet

GET

/v1/{chainName}/address/{walletAddress}/portfolio_v2/

Historical portfolio for a wallet

GET

/v1/{chainName}/address/{walletAddress}/transfers_v2/

ERC-20 transfers for a wallet

GET

/v1/{chainName}/address/{walletAddress}/balances_nft/

NFT holdings for a wallet

GET

/v1/{chainName}/events/address/{contractAddress}/

Log events by contract address

GET

/v1/{chainName}/events/topics/{topicHash}/

Log events by topic hash

GET

/v1/chains/

List supported chains

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the GoldRush Multichain Data API by hand means learning its bearer auth, pinning the api.covalenthq.com host, and coding your own per-chain, per-address read requests. Through Jentic you install once, import the GoldRush API from the API Directory, store the token once, and your agent calls it.

Permission scoping

GoldRush is a read-only data API where the chain name and wallet address are lookup values in the path, not permissionable resources, so scope by operation: limit the agent to the operations it needs, such as reading token balances, a portfolio, or transfers for an address. You choose the operations it may call, so it stays limited to those reads.

Credential isolation

Your GoldRush token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get token balances for a wallet' or 'list NFT holdings on a chain', and Jentic returns the matching GoldRush operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GoldRush Multichain Data APIs through Jentic.

Why is there no official OpenAPI spec for GoldRush Multichain Data APIs?

Covalent does not publish a single OpenAPI specification for GoldRush. Jentic generates and maintains this spec so that AI agents and developers can call GoldRush Multichain Data APIs via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the GoldRush API use?

GoldRush authenticates via an HTTP bearer token. Pass your GoldRush API key as `Authorization: Bearer <token>`. Through Jentic, the key is stored encrypted in your Jentic One instance and the agent receives a scoped session token rather than the raw key.

Can I get token balances across many chains in one call?

The /v1/{chainName} endpoints return data for one chain per call, but GET /v1/allchains/address/{walletAddress}/balances/ returns token balances for a wallet across all supported chains in a single response. Use it when the UI does not need per-chain isolation.

How do I check if a wallet owns a specific NFT?

Call GET /v1/{chainName}/address/{walletAddress}/collection/{collectionContract}/token/{tokenId}/. The response confirms ownership of the exact token ID in the collection contract on the given chain. Use it for token-gated experiences.

What are the rate limits for the GoldRush API?

Rate limits and chain coverage depend on the GoldRush plan attached to the API key. Free tiers cap requests per second and limit some premium chains; paid plans raise both. Cache responses such as historical balances aggressively because they rarely change after the fact.

How do I look up a wallet through Jentic?

Search Jentic for 'get token balances for a wallet', load the schema for GET /v1/{chainName}/address/{walletAddress}/balances_v2/, and execute it with the chain name (e.g. eth-mainnet) and wallet address. Jentic supplies the bearer token from the vault.

Does GoldRush support Bitcoin?

Yes. GET /v1/btc-mainnet/address/{walletAddress}/balances_v2/ returns Bitcoin balances and /hd_wallets/ returns HD wallet balances. /historical_balances/ returns the historical curve. EVM and Bitcoin endpoints share the same bearer auth scheme.

Can I limit what my agent is allowed to do with the GoldRush API?

Yes. GoldRush is a read-only data API, so you scope by operation: in your self-hosted Jentic One instance, your own rules decide which GoldRush reads the agent may call. You can allow only the operations it needs, such as fetching token balances, a historical portfolio, or ERC-20 transfers for an address, and withhold the rest like NFT ownership checks or log-event queries. The chain name and wallet address are just path lookup values, so the agent stays confined to the read operations you have granted and the credential you have stored.