Address Counterparties
In this model, we are listing the addresses or entities which have the most common interactions with the input addresses. The model is able to show volume in, volume out and number of transactions in and out for tokens, eth and combined.
Successful response
Bad request
Authentication error
Forbidden - Subscription tier required
Internal server error
POST /api/beta/profiler/address/counterparties HTTP/1.1
Host: api.nansen.ai
apiKey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 241
{
"parameters": {
"walletAddresses": [
"0x28c6c06298d514db089934071355e5743bf21d60"
],
"chain": "ethereum",
"sourceInput": "Combined",
"groupBy": "wallet",
"timeRange": {
"from": "2025-05-01",
"to": "2025-05-03"
}
},
"pagination": {
"page": 1,
"recordsPerPage": 100
}
}
[
{
"chain": "text",
"interactingWalletAddress": "text",
"interactingWalletLabel": "text",
"volumeOut": "text",
"volumeIn": "text",
"numberOfOutgoingTransactions": "text",
"numberOfIncomingTransactions": "text",
"netInflowInUsd": "text",
"info": "text"
}
]
Usage Tips
Querying Counterparties across all chains
You can also query balances across all chains using this
"chain": "all",
Querying Entity Counterparties
You can also pull counterparties for any labelled entity (eg. Binance, Alex Svanevik, Paradigm Fund) instead of raw addresses.
Provide exactly one of:
walletAddresses – array of addresses or
entityId – string name of the entity
Leave the other field empty / omitted.
All other parameters behave the same.
Example request — entity lookup
POST /api/beta/profiler/address/counterparties
Host: api.nansen.ai
apiKey: YOUR_API_KEY
Content-Type: application/json
{
"parameters": {
"walletAddresses": [],
"entityId": "Alex Svanevik",
"chain": "base",
"sourceInput": "Combined",
"groupBy": "wallet",
"timeRange": {
"from": "2025-05-11",
"to": "2025-05-21"
}
},
"pagination": {
"page": 1,
"recordsPerPage": 100
}
}
Last updated
Was this helpful?