Find wallets related to a blockchain address through on-chain interactions via Nansen's profiler API.
What it does
This endpoint returns wallets that are related to a given blockchain address through various types of on-chain interactions and relationships. It is part of Nansen's Profiler suite and accepts a POST request with an address and chain parameter. The response includes detailed information about each related wallet: the relationship type, transaction details, timing information, and address labels.
The endpoint supports 24 chains including Ethereum, Solana, Bitcoin, Base, Arbitrum, Polygon, and others. Results are paginated (up to 1000 per page) and can be sorted by a default ordering field. The x-payment-info in the OpenAPI spec indicates a fixed price of $0.01 per call via the x402 protocol, and the probe confirmed the endpoint is live (HTTP 402 challenge returned). Credit costs are 10 credits on the free tier and 1 credit on the pro tier.
This is useful for wallet clustering, compliance investigations, identifying funding sources, and mapping entity relationships across blockchains. The related-wallets data complements other Nansen profiler endpoints like counterparties, transactions, balances, and PnL analysis.
Capabilities
Use cases
- —Identify wallets controlled by the same entity through funding and interaction patterns
- —Map the on-chain social graph of a specific address for compliance or research
- —Discover funding sources and related addresses for due diligence
- —Automate wallet clustering in investigative or analytical pipelines
- —Enrich address profiles with relationship context before trading decisions
Fit
Best for
- —Blockchain investigators tracing fund flows and wallet ownership
- —Compliance teams performing KYC/AML address screening
- —Quantitative researchers building wallet-entity graphs
- —AI agents that need to expand an address into its related cluster
Not for
- —Real-time trading signals or price data
- —Off-chain identity resolution (no PII returned)
- —Free-tier bulk scraping (credit-gated, 10 credits per call on free plan)
Quick start
curl -X POST https://api.nansen.ai/api/v1/profiler/address/related-wallets \
-H 'Content-Type: application/json' \
-H 'Payment-Signature: <x402_payment>' \
-d '{"address": "0x28c6c06298d514db089934071355e5743bf21d60", "chain": "ethereum", "pagination": {"page": 1, "per_page": 10}}'Example
Request
{
"chain": "ethereum",
"address": "0x28c6c06298d514db089934071355e5743bf21d60",
"pagination": {
"page": 1,
"per_page": 10
}
}Response
{
"data": [
{
"chain": "ethereum",
"order": 1,
"address": "0x742d35cc6634c0532925a3b8d4c9db96c4b4d8b6",
"relation": "funded_by",
"address_label": "Binance Hot Wallet",
"block_timestamp": "2024-06-15T08:30:00Z",
"transaction_hash": "0xabc123def456..."
}
],
"pagination": {
"page": 1,
"per_page": 10,
"is_last_page": false
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed request/response models, live 402 challenge confirmed, clear pricing ($0.01/call), and 24 supported chains documented. Docked slightly because no example response was captured from the live endpoint and crawled docs pages returned 404s (only the OpenAPI spec was available).
Warnings
- —No standalone documentation pages found at api.nansen.ai/docs or similar paths; all info derived from OpenAPI spec.
- —Example response is inferred from the schema, not captured from a live call.
Citations
- —Endpoint price is $0.01 per call via x402 protocolhttps://api.nansen.ai/openapi.json
- —Credit cost is 10 (free tier) / 1 (pro tier) per callhttps://api.nansen.ai/openapi.json
- —Supports 24 chains including ethereum, solana, bitcoin, base, arbitrum, polygon, etc.https://api.nansen.ai/openapi.json
- —Endpoint returns related wallets with relationship type, transaction hash, timestamp, and address labelshttps://api.nansen.ai/openapi.json
- —Endpoint is live and returned HTTP 402 x402 payment challengehttps://api.nansen.ai/api/v1/profiler/address/related-wallets