Onchain intelligence platform with deanonymized entity labels, fund-flow tracking, transfers, and historical balances across 10+ chains.
- 01entity-level wallet labeling
- 02fund-flow visualization
- 03whale and exchange tracking
- 04transfer-history feeds
- 05compliance-adjacent investigations
| Variable | Scope | Description |
|---|---|---|
| ARKHAM_API_KEY | Server | Arkham Intel API key (request access via intel.arkm.com). Server-only. |
Use the Arkham Intel API for entity labels and fund-flow data. From the server, call `https://api.arkhamintelligence.com/{path}` with header `API-Key: $ARKHAM_API_KEY`. Key endpoints: `GET /intelligence/address/{address}` for the entity + label profile, `GET /transfers?base={address}` for inbound/outbound transfers, and `GET /balances/address/{address}` for current holdings. Always treat entity labels as hints (high signal but not legal proof) and surface the `arkhamEntity.type` (cex/fund/individual) in your UI.
- ⚑API access is gated — you must apply and be approved; there is no instant self-serve key.
- ⚑Auth header is `API-Key` (capital K, hyphen), not `Authorization` or `x-api-key` — easy to misconfigure.
- ⚑Entity labels are crowdsourced + ML-derived; treat them as probabilistic, never as the sole basis for a compliance decision.
- ⚑Chain coverage is narrower than Nansen/Etherscan — verify each chain you need is on the supported list before designing around it.
- ⚑Rate limits and quotas are tier-dependent and not fully published; build in 429 backoff and ETag/conditional caching.