Goldsky

Wallet balances and history for your app

Goldsky’s Balances and Transfers APIs return what a customer holds and how it moved, priced in US dollars, so wallets, neobanks and payment apps can show it without building their own indexer.

Talk to our team

Read the guide

At a glance

Token balances with USD values and a total
Transfer history, priced at the time of each transfer
REST requests from your existing backend
Webhooks when tracked activity changes

Trusted by wallet, fintech and payment teams

Your engineers work on the screens

Showing a crypto balance means reading several blockchains, decoding tokens and pricing them. Goldsky does that part.

Prices are already attached
The Balances and Transfers feeds already include USD values, so your engineers can work on the portfolio and activity screens from the start.
Cross-checked chain reads
When your app needs to read a blockchain directly, Edge RPC compares answers from several nodes and switches providers when one fails.
No indexer to maintain
Goldsky indexes, normalizes and prices the data behind Feeds. Your team doesn’t have to keep that system running.

Wallet balance and transaction history APIs

Start with the Balances and Transfers feeds. Edge RPC, Subgraphs and Turbo Pipelines cover direct reads, custom history and data you want to keep yourself.

Balances

One request returns a wallet’s native coin and ERC-20 tokens, each with a USD value, plus the wallet total.

Activity

The Transfers feed lists a wallet’s transfers in and out, newest first, with each one’s USD value when it happened.

Direct reads

Edge RPC answers your app’s own blockchain requests over HTTPS, with caching and failover between providers.

Custom history

A subgraph indexes the activity you choose and serves it through a GraphQL API that Goldsky hosts. Use it for statements shaped to your product.

Webhooks

Subgraph webhooks tell your backend when something changes, so notifications and support tools don’t have to poll.

Your own copy

If you want to hold balances and history yourself, Turbo Pipelines stream the data into your database, warehouse or queue.

Built for regulated environments

SOC 2 Type II, dedicated and on-premises deployment, and access controls for banks, payment companies and trading firms.

SOC 2 Type II

Goldsky maintains SOC 2 Type II compliance.

Dedicated infrastructure

Single-tenant infrastructure in Goldsky-managed cloud accounts, with static IPs for allowlisting, on Enterprise.

On-premises and BYOC

Run the full stack on-prem or in your own cloud, so data and compute stay inside your boundary.

Access controls

Role-based access on every plan, plus SAML SSO and audit logs on Enterprise.

Complete, validated data

Every block is checked for completeness before delivery, and daily validation repairs any gaps.

Data for your compliance program

Transfer and identity data for MiCA, Travel Rule and BSA/AML: Goldsky supplies it, your team owns the program.

Deliver on your timeline

Banks, payment companies and trading firms use Goldsky to get onchain products live in weeks. Our engineers work with yours from the first call to production.

Scoping call

We learn what your digital asset product needs and give you a delivery estimate.

Proof of concept

Our engineers and yours build a working version on your own data.

Kickoff and go live

We launch it together and check the numbers against your systems.

Ongoing support

24/7 support in a shared channel with the engineers who run your infrastructure.

Step 1
Scoping call
We learn what your digital asset product needs and give you a delivery estimate.
Step 2
Proof of concept
Our engineers and yours build a working version on your own data.
Step 3
Kickoff and go live
We launch it together and check the numbers against your systems.
Ongoing
Ongoing support
24/7 support in a shared channel with the engineers who run your infrastructure.

Book a scoping call

Build wallet balance and history screens today

Copy the prompt into your AI coding agent and build a working version today.

Open in Claude Code

I'm building wallet balance and transaction history screens using Goldsky.

## Set up your tooling first

```bash
npx skills add goldsky-io/goldsky-agent
```

That installs to Claude Code, Cursor, Codex, Windsurf and 30+ other agents. Then connect Goldsky's MCP server at `https://docs.goldsky.com/mcp` however your tool does it — per-client setup is at https://docs.goldsky.com/mcp-server

Finally, use the `auth-setup` skill to install the Goldsky CLI if it's missing, and confirm I'm logged in before you start.

## What I'm building

Follow the Goldsky guide at https://docs.goldsky.com/feeds

Help me:

1. Pull live wallet balances through the Feeds API for the balance screen
2. Pull paginated transfer history through the Feeds API for the activity screen
3. Write a check in our backend that compares balance reads against Edge RPC before they reach the app
4. Set up a webhook so our backend is notified of new activity on the wallets we track

## How to work

- Confirm dataset names yourself rather than assuming them
- Write the files, and create any Goldsky secrets the pipeline needs
- Validate locally — `goldsky turbo validate` for pipelines, a local task call for Compose
- Ask me for anything you can't determine: contract addresses, endpoints, thresholds, which database we're writing to
- Put credentials straight into Goldsky secrets, never into this chat

**Stop before deploying anything live**, then show me the commands to run.

Give customers balances they can trust

Bring your app and the chains your customers use to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

Which chains are covered?

It depends on the product. Feeds, Edge RPC and Subgraphs each publish their supported chains in the Goldsky docs.

Can the app get updates over WebSockets?

Not from Edge RPC, which is HTTPS only. Your app can poll, or Turbo Pipelines can stream changes into your database or a queue.

How much work is this for our engineers?

Feeds is REST requests from the backend you already have. Subgraphs take more setup because your team decides what gets indexed, but Goldsky runs the indexing and storage.