Arkham Labels Scraper

Scrape Arkham Intelligence labels, entity names, and on-chain tags for wallet addresses in bulk — one result row per blockchain network, at ~100 addresses per second.

For every address you submit, this Actor returns the data Arkham shows on its platform:

• Label / title — e.g. Binance: Hot Wallet, Coinbase: Cold Wallet
• Entity name — the organization behind the address (Binance, OKX, Deribit...)
• On-chain tags — e.g. Centralized Exchange, Hot Wallet, Mixer, UK Sanctioned, High Transacting, first-funder relationships, and more
• Contract flag and per-network breakdown across Ethereum, Arbitrum, Base, BSC, Polygon, Avalanche, and other supported chains

Typical uses: labeling exchange wallets for compliance and AML screening, enriching address datasets for on-chain analytics, identifying CEX hot/cold wallets, and research on sanctioned or high-risk addresses. A 5,000-address list completes in about a minute.

How to run

1. Open the Actor and go to Input.
2. Provide addresses in one of these ways:
   • Addresses CSV (file upload) — CSV with an address column
   • Addresses CSV (URL) — link to a CSV with the same format
   • Addresses (JSON) — e.g. ["0xabc...", "0xdef..."]
3. Set Maximum cost per run (see below) high enough for your list size.
4. Click Start.

Try it instantly: the input form comes pre-filled with a few example addresses (Binance wallets) — just click Start to see the output format.

Example CSV

Only the address column is required; the optional columns are carried through to your output rows unchanged:

address,blockchain,cex_name
0x835678a611B28684005a5e2233695fB6cbbB0007,ethereum,Binance
0x28C6c06298d514Db089934071355E5743bf21d60,ethereum,Binance
0x21a31Ee1afC51d94C2eFcCAa2092aD1028285549,ethereum,Binance
0x5041ed759Dd4aFc3a72b8192C143F72f4724081A,ethereum,OKX
0x1157A2076b9bB22a85CC2C162f20fAB3898F4101,ethereum,

Example JSON

["0x835678a611B28684005a5e2233695fB6cbbB0007", "0x28C6c06298d514Db089934071355E5743bf21d60"]

Pricing & budget

You are charged per address attempted (each lookup), not per network/tag row in the Dataset. That includes addresses that return no useful data or fail the lookup.

Example	Math
Price	$3 per 1,000 addresses → $0.003 per address
500 addresses (full run)	≈ $1.50
1,000 addresses (full run)	≈ $3.00

Maximum cost per run

On the Start screen, Maximum cost per run caps how much this run can bill.

• If your list needs more money than that cap, the Actor stops when the budget is used up.
• No further addresses are looked up after that.
• The run status/log will say the maximum cost was reached and that you should raise the limit to continue.

Example: 1,000 addresses with Maximum cost = $1 → about 333 addresses are attempted and billed (~$1). The other ~667 are skipped.

Set Maximum cost per run to at least:

addresses ÷ 1000 × $3

(e.g. 5,000 addresses → at least $15).

The Actor default is $300 (enough for the full 100,000-address run limit). You can lower it on the Start screen for small lists.

Run limits

• One run processes up to 100,000 addresses (~$300 at the base price). If your list is larger, the run processes the first 100,000, reports how many were skipped, and you run the remainder separately.
• A 100,000-address run typically completes in under 20 minutes; a 5,000-address list takes about a minute.

Output

Results appear in the run’s Dataset tab. Export as CSV, JSON, or Excel.

Field	What it is
query_address	Address you submitted
network	Blockchain (e.g. ETHEREUM, ARBITRUM)
address	Address on that network
title	Arkham title (e.g. Binance: Hot Wallet)
entity_name / label_name	Entity and label, if any
chain_tags	Tags on that network
is_contract	Whether it’s a contract

Notes

• Failed / invalid / unreachable addresses are skipped in the Dataset; you are still charged for the attempt. The run log lists them, and the final status summarizes how many failed.
• You are charged per address attempted, not per network row.
• Raise Maximum cost per run if you need the full list processed in one run.