Partner Contribute API

What this API is

The Contribute API lets partner organizations submit known-address labels — exchange wallets, scam addresses, issuer wallets — into the ChainAnalyzer registry. It is built for VASP and AML partner teams: you contribute what your organization has already verified, without needing an admin account.

Submitted entries are stored with status="pending" and reviewed by a ChainAnalyzer analyst. Once approved they become status="active" and start informing scans, screening decisions and registry lookups.

Who it is for: exchanges, custodians, issuers and AML vendors that hold verified address intelligence of their own.

Authentication

Every request requires an X-Contributor-API-Key header. Keys carry a cak_ prefix and are issued by ChainAnalyzer per organization — they cannot be self-provisioned.

curl -H "X-Contributor-API-Key: cak_your_key_here" \

     https://chain-analyzer.com/api/v1/contribute/whoami

Each key is scoped to your organization (allowed categories and chains) and is revocable at any time. Submitting a chain or category outside your scope returns 403.

Contact us to have a key issued. The plaintext key is shared once at issuance and cannot be retrieved again.

Keep the key server-side. Never embed it in a browser or mobile client. If you suspect it has leaked, tell us and we will revoke it immediately.

Endpoint

POST https://chain-analyzer.com/api/v1/contribute/known-entity

Request body

Valid enums

registry_type

chain

Address normalization

Addresses on EVM chains (ethereum, polygon, bsc, base, arbitrum, optimism, avalanche, kaia, evm) are lowercased before storage. btc, solana, tron and xrp are base58-family and case-sensitive, so they are stored exactly as submitted — send them with their original casing intact.

Example request

Submitting an exchange hot wallet on TRON:

curl -X POST https://chain-analyzer.com/api/v1/contribute/known-entity \
  -H "X-Contributor-API-Key: cak_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "registry_type": "exchange",
    "chain": "tron",
    "address": "TXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
    "label": "ExampleExchange Hot 1",
    "category": "exchange_hot_wallet",
    "metadata": {
      "exchange_name": "ExampleExchange",
      "wallet_type": "hot"
    },
    "verification_source": "internal treasury records",
    "notes": "Primary TRC-20 settlement wallet, active since 2025-11."
  }'

Response

A successful submission returns 201 Created with the id of the pending entry.

HTTP/1.1 201 Created

{
  "ok": true,
  "id": "3d1f0c6e-5a2b-4f19-8f7a-0c9d2e6b41aa",
  "status": "pending",
  "message": "Submission queued for admin review. You will be notified when reviewed."
}

Errors

Review flow

1. The entry is stored as status="pending" and the ChainAnalyzer review queue is notified.
2. An analyst checks the evidence. Entries carrying a verification_source are processed first.
3. On approval the entry becomes status="active" and starts informing scans, screening and registry lookups. Entries with insufficient evidence are held as disputed.

Verifying your key

Before submitting, call /contribute/whoami to confirm the key and see the scopes in effect. It writes nothing to the registry.

curl -H "X-Contributor-API-Key: cak_your_key_here" \
  https://chain-analyzer.com/api/v1/contribute/whoami

Submission guidance

• Only submit addresses your organization can verify. Hearsay and inference do not survive review.
• Write labels in English, as "operator + role" (e.g. "ExampleExchange Hot 1", "ExampleExchange Deposit Sweep").
• For exchange wallets, put exchange_name and wallet_type (hot / cold / deposit / withdrawal) in metadata.
• For illicit addresses, always attach evidence that pins down the incident or method — a public report, a case number, or your internal investigation ID.
• One address per request. Iterate client-side when submitting in bulk.
• Do not submit speculative labels. A wrong label costs every investigation that later relies on it.