x402basequality 0.88

Nansen address counterparties: top transaction partners, volume, and flow analysis for any wallet via x402

Price
per_call
Protocol
x402
Verified
no

What it does

The Nansen Profiler Address Counterparties endpoint returns the top counterparties that a given wallet address or entity has interacted with on-chain. It supports grouping by wallet or entity and filtering by source type (Combined, Tokens, ETH). The response includes interaction statistics such as transaction count, total volume in USD, inflow/outflow breakdowns, timing data, and token details per counterparty. Smart money label filtering (include/exclude) is available, along with premium label support.

This endpoint is part of the broader Nansen API v1, which provides blockchain analytics across 25+ chains including Ethereum, Solana, Base, Arbitrum, and others. The counterparties endpoint specifically requires a chain parameter and a date range. It accepts POST requests with a JSON body. Payment is handled via the x402 protocol at $0.05 per call (fixed pricing). The API also supports traditional API key authentication with a credit-based system (50 credits on free tier, 5 on pro).

Results are paginated (up to 1000 per page) and sortable by interaction_count, total_volume_usd, last_interaction_date, volume_in_usd, or volume_out_usd. High-volume addresses are limited to 180-day lookback windows. The endpoint returns labeled counterparty addresses with Nansen's proprietary labeling system.

Capabilities

wallet-counterparty-analysison-chain-interaction-statsvolume-inflow-outflowsmart-money-label-filteringmulti-chain-supportentity-groupingpaginated-resultsx402-payment

Use cases

  • Identify the most frequent transaction partners of a wallet by count and volume
  • Analyze net value flows between addresses to detect funding sources
  • Map exchange and DeFi protocol interaction patterns for a specific wallet
  • Investigate high-value transfer relationships for compliance or research
  • Build wallet relationship graphs for on-chain intelligence

Fit

Best for

  • On-chain investigators analyzing wallet interaction patterns
  • Trading desks profiling counterparty relationships
  • Compliance teams mapping fund flows between entities
  • Researchers studying DeFi protocol usage by specific wallets

Not for

  • Real-time trade execution or order routing
  • Historical price or OHLCV data (use the TGM token-ohlcv endpoint instead)
  • Bulk scanning of thousands of wallets simultaneously (rate-limited)

Quick start

curl -X POST https://api.nansen.ai/api/v1/profiler/address/counterparties \
  -H 'Content-Type: application/json' \
  -H 'X-Payment: <x402_payment_header>' \
  -d '{
    "address": "0x28c6c06298d514db089934071355e5743bf21d60",
    "chain": "ethereum",
    "date": {"from": "2025-05-01T00:00:00Z", "to": "2025-05-03T23:59:59Z"},
    "pagination": {"page": 1, "per_page": 10}
  }'

Example

Request

{
  "date": {
    "to": "2025-05-03T23:59:59Z",
    "from": "2025-05-01T00:00:00Z"
  },
  "chain": "ethereum",
  "address": "0x28c6c06298d514db089934071355e5743bf21d60",
  "group_by": "wallet",
  "pagination": {
    "page": 1,
    "per_page": 10
  },
  "source_input": "Combined"
}

Response

{
  "data": [
    {
      "tokens_info": [
        {
          "token_name": "USD Coin",
          "num_transfer": "15",
          "token_symbol": "USDC",
          "token_address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
        }
      ],
      "volume_in_usd": 800000.25,
      "volume_out_usd": 450000.25,
      "total_volume_usd": 1250000.5,
      "interaction_count": 42,
      "counterparty_address": "0x742d35cc6634c0532925a3b8d4c9db96c4b4d8b6",
      "counterparty_address_label": [
        "Binance Hot Wallet"
      ]
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 10,
    "is_last_page": false
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x93053f1e7A5eFEDa532Fe69CbbE43cBEc3A0F13f
CurrencyUSD COIN

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with detailed request/response models, clear pricing ($0.05/call via x402), and a confirmed live 402 challenge. The endpoint description is thorough with filter options and sort fields. Minor deduction because no example response was directly captured from the probe (only schema-inferred), and crawled docs pages returned 404s.

Warnings

  • No dedicated documentation pages were reachable (all returned 'no Route matched'); schema is the sole source of endpoint details.
  • Response example is inferred from the OpenAPI schema, not captured from a live call.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:40:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access