Recipe 22 of 32
Wallet activity summary: volume, inflow and outflow from 24h to all time
/wallets/{address} returns volume, inflow, outflow, net flow and transfer count for 24h, 7d, 30d, 90d and all time in one response.
One call to GET /v1/onchain/wallets/{address} returns five windows at once: 24h, 7d, 30d, 90d and all. Each carries
total_volume, total_inflow, total_outflow, net_flow and tx_count, in plain USD, and the top-level chain
names the chain that answered. The full parameter list is on Wallet summary.
Quick answer
# vitalik.eth's activity in every window, one response
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/onchain/wallets/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"Example response
Captured from the live API on 2026-10-24 at 17:18 UTC, trimmed to 3 of the 5 windows.
total_volume is inflow plus outflow, and net_flow is inflow minus outflow. first_seen, last_active and
tokens_traded are all-time figures repeated in every window, so read them from all. The wallet is long-lived
and quiet: 435,011 transfers since 2016, 38 in the last 30 days.
{
"chain": "ethereum",
"all": {
"total_volume": 144128716.070085,
"total_inflow": 54578966.300201,
"total_outflow": 89549749.769884,
"net_flow": -34970783.469683,
"tx_count": 435011,
"tokens_traded": 12378,
"first_seen": "2016-05-06",
"last_active": "2026-10-23"
},
"30d": {
"total_volume": 2893.082798,
"total_inflow": 63.443396,
"total_outflow": 2829.639402,
"net_flow": -2766.196006,
"tx_count": 38,
"tokens_traded": 12378,
"first_seen": "2016-05-06",
"last_active": "2026-10-23"
},
"24h": {
"total_volume": 1.448407,
"total_inflow": 1.448407,
"total_outflow": 0.0,
"net_flow": 1.448407,
"tx_count": 2,
"tokens_traded": 12378,
"first_seen": "2016-05-06",
"last_active": "2026-10-23"
}
}Variations
Another chain. Name the chain to get that chain's figures.
# the same wallet on Base
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/onchain/wallets/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?chain=base"One line per window. Flatten the response into window, inflow, outflow and net flow.
# one row per window
curl -s -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/onchain/wallets/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045" \
| jq 'del(.chain) | to_entries | map({window: .key, inflow: .value.total_inflow, outflow: .value.total_outflow, net: .value.net_flow})'An exchange hot wallet. The same read on a much busier address, Binance 14.
# Binance 14's windows
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/onchain/wallets/0x28C6c06298d514Db089934071355E5743bf21d60"Before you rely on it
Without chain, one chain answers
With no chain, the route answers for the more recently active of ethereum and bsc, and for base or
hyperevm only when the wallet has no priced volume on the first two. The response never adds chains together.
For the four chains, call once per chain; an address with no transfers on the chain answers chain: null with
every figure 0.
Windows are calendar days, tx_count counts transfers
The 24h window covers yesterday and today in UTC, and 7d covers today plus the 7 days before. tx_count counts
token transfers in either direction, unpriced ones included, while the USD figures count priced transfers only.
Ask your agent
Connected to the Vike MCP server (https://vike.io/mcp) in Claude, ChatGPT or Cursor, ask it in plain words.
The wallet_summary tool answers it, at 2 credits a call.
Give me the activity summary of vitalik.eth: volume, inflow and outflow for every window