Counterparties

profiler/address/counterparties

post

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.

Authorizations

Body

Responses

200

Successful response

application/json

400

Bad request

application/json

401

Authentication error

application/json

403

Forbidden - Subscription tier required

application/json

500

Internal server error

application/json

post

HTTPcURLJavaScriptPython

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"
  }
]

profiler/address/related-wallets

post

This model provides information about related wallets of an input address. The relation can be any of 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'.

Questions you can answer using this model are:

1. What addresses are related to a specific address?

2. In which way is an address related to other addresses?

3. Did the specified address deploy any contracts?

4. Where did the specified address get its first funds from?

Authorizations

Body

Responses

200

Successful response

application/json

400

Bad request

application/json

401

Authentication error

application/json

403

Forbidden - Subscription tier required

application/json

500

Internal server error

application/json

post

HTTPcURLJavaScriptPython

POST /api/beta/profiler/address/related-wallets HTTP/1.1
Host: api.nansen.ai
apiKey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 145

{
  "parameters": {
    "chain": "ethereum",
    "walletAddresses": [
      "0x28c6c06298d514db089934071355e5743bf21d60"
    ]
  },
  "pagination": {
    "page": 1,
    "recordsPerPage": 100
  }
}

[
  {
    "addressHex": "text",
    "addressName": "text",
    "relation": "text",
    "transactionHash": "text"
  }
]

Performance Tips

To ensure optimal performance when using the counterparties API:

• Limit the number of chains included in a single request. We recommend querying one chain at a time.

• Use a shorter `look-back` window, such as 1 month, for faster response times.

• Avoid querying very large timeframes.