Counterparties, trace & compare
Who a wallet deals with: its top counterparties by transfer volume, a multi-hop trace of the money in, out or both, and the counterparties and tokens two wallets share, each with labels.
Who a wallet deals with: its top counterparties by transfer volume, a multi-hop trace of the money in, out or both, and the counterparties and tokens two wallets share, each with labels.
How to get it
- REST —
GET /v1/onchain/wallets/{address}/counterparties - REST —
GET /v1/onchain/wallets/{address}/trace - REST —
GET /v1/onchain/wallets/compare - MCP — tool
wallet_counterpartiesonhttps://vike.io/mcp.
Sample call
A call (replace each {placeholder}):
curl -s "https://data.vike.io/v1/onchain/wallets/{address}/counterparties" \
-H "X-API-KEY: $VIKE_API_KEY"Built on
Derived from these datasets, directly or through aggregate tables:
- Token transfers — Who bought and who sold a token over a period, aggregated from raw transfers.
- Wallet labels — Entity, wallet type and risk flag per address — plus which source claimed what.
Wallet discovery
A leaderboard of active wallets on one chain, ranked by volume, inflow, outflow, net flow, transaction count or realized PnL over 24h, 7d, 30d, 90d or all time (on Base and HyperEVM the rolling windows only while their daily refresh is under 2 days old); round-trip hubs are hidden by default.
First funder, exchange usage & transactions
A wallet's earliest inbound native and token transfers with each sender's label, the centralised exchanges it sent to and received from, and its raw transfer list.