MPPtempoquality 0.82

Discover first-degree wallet relationships and related addresses via Nansen's on-chain profiler.

Price
$0.01 / call
Protocol
mpp
Verified
no
Endpoint
https://api.nansen.ai/api/v1/profiler/address/related-wallets

What it does

The Nansen Related Wallets endpoint identifies wallets that are connected to a given input address through various types of blockchain interactions. For each related wallet it returns the relationship type, the linking transaction hash, timestamp, and ordering information. It supports 24+ chains including Ethereum, Solana, Bitcoin, Base, Arbitrum, Polygon, and more.

This endpoint is part of Nansen's broader Profiler API suite, which also covers address balances, PnL, counterparties, labels, transactions, and historical balances. The related-wallets endpoint accepts a POST request with an address and chain parameter, and returns paginated results. It costs 10 credits on the free tier or 1 credit on the pro tier per call, and is also available via the x402 pay-per-request protocol at $0.01 per call. Rate limits include per-second and per-minute windows, reported via response headers.

The API is documented via a full OpenAPI 3.1 spec served from api.nansen.ai. Authentication is via an `apiKey` header. The endpoint returned HTTP 402 on probe, confirming it is live and gated behind payment. The response schema includes fields for address, address_label, relation, transaction_hash, block_timestamp, order, and chain.

Capabilities

wallet-profilingrelated-walletsfirst-degree-relationsmulti-chainblockchain-analyticsaddress-graphon-chain-intelligencex402-paymentpaginated-results

Use cases

  • —Map first-degree wallet relationships for compliance or investigation workflows
  • —Identify related wallets to detect sybil or wash-trading patterns
  • —Enrich wallet profiles in trading bots by discovering linked addresses
  • —Build address graphs for on-chain forensics or fund-flow analysis
  • —Discover entity structures by tracing wallet connections across chains

Fit

Best for

  • —On-chain investigators needing first-degree wallet connections
  • —Trading agents enriching address context before executing
  • —Compliance teams mapping wallet clusters across multiple chains
  • —Researchers building address relationship graphs

Not for

  • —Real-time sub-second trading signals (API has rate limits and latency)
  • —Off-chain identity resolution or KYC (returns on-chain relations only)
  • —Free-tier heavy usage without credits (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 'apiKey: YOUR_API_KEY' \
  -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

URLhttps://api.nansen.ai/api/v1/profiler/address/related-wallets
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.82/ 1.00

Full OpenAPI 3.1 schema with detailed request/response models, clear pricing ($0.01/call via x402, 10/1 credits free/pro), and confirmed live 402 response. Docked slightly because no crawled documentation pages were available (all returned routing errors) and the example response is inferred from the schema rather than captured.

Warnings

  • —No external documentation pages were reachable (docs, pricing, README all returned 404-like routing errors)
  • —Example response is synthesized from the OpenAPI schema, not captured from a live call
  • —The probe did not capture a full x402 or MPP challenge body, only a bare 402 status

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 15:54:39Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/TRKFjA