address_counterparties_batch

io.github.nansen-ai/nansen-mcp · Verify this server

Get the top counterparties of up to 10 wallet addresses in one call. Every wallet gets its own counterparty list. The lists are NOT added together: the answer has one table for each wallet. Use this tool to compare wallets — counterparties that two wallets share, a group of wallets that sends to the same CEX deposit address, or one fund with many wallets. For one wallet, or for an entity name, use address_counterparties. Limits: - Maximum 10 distinct wallet addresses for each call. Repeated addresses are removed. - Maximum 90 days for the date range. A wider range is rejected — make more than one call. - One chain family for each call: every address must be EVM, or every address must be Solana, and so on. Do not mix families. Name a `chain` (for example ethereum) to read that chain only. Leave `chain` out to read every chain of the addresses' family at one time — then a counterparty met on more than one chain gets one row for each chain, so do not add those rows together. Sorting Options (all fields support "ASC"/"DESC"): Available for sorting: total_volume_usd, volume_in_usd, volume_out_usd, interaction_count. The sort is applied inside each wallet's block. Example (every key below is the name the request accepts, and the addresses are real — copy this shape as it stands): { "walletAddresses": [ "0x28c6c06298d514db089934071355e5743bf21d60", "0xd8da6bf26964af9d7eed9e03e53415d37aa96045" ], "chain": "ethereum", "timeRange": {"from": "30D_AGO", "to": "NOW"}, "sourceInput": "Combined", "orderBy": "total_volume_usd", "orderByDirection": "DESC", "perPage": 100 }