Skip to main content
GET
Token - Holder Profile

Cohort-level holder summary for labeled wallets.

  • Supported holder tags are bundler, sniper, insider, dev, smart_trader, and kol.
  • holder_summary aggregates all labeled holders returned by the profile.
  • tags breaks the token down by holder label, with holder count, held amount, supply share, buy/sell volume, average buy price, and PnL.
  • top10_holder summarizes the token’s top 10 holders separately from labeled cohorts.
  • include_zero_balance=true includes wallets that traded the token but no longer hold it.
  • This endpoint consumes 25 CU per request.
  • dev — The wallet that created the token: the mint creator from the initialize-mint transaction.
  • sniper — A wallet that bought within the first n blocks of the token, counted from the token’s first swap. On Solana, n = 5; a buy qualifies when its slot is within first_trade_slot + 5.
  • bundler — Coordinated buying detected in either level:
  • Level 1: at least 4 buy transactions in the same slot.
  • Level 2: at least 3 distinct wallets buying across adjacent slots, where max slot gap is 1.
  • insider — A wallet that received the token directly from the Chef wallet via token transfer, not via a swap.
  • smart_trader — A non-bot wallet ranked in Top Realized PnL over the last 90 days with realized PnL > $10,000. Wallets identified as bots are excluded before ranking and never receive this tag.
  • kol — A tracked key-opinion-leader wallet label for this token when Birdeye classification identifies the wallet as a KOL cohort member.
  • Compress token-holder intelligence into one executive snapshot: market context, top-holder concentration, labeled-holder exposure, and cohort-level PnL.
  • Score token quality by comparing how much supply is controlled by bundlers, snipers, insiders, developers, smart traders, and KOL cohorts.
  • Build risk panels that highlight whether suspicious cohorts dominate supply or whether higher-quality smart-money wallets are participating.
  • Track cohort conviction through hold amount, percent of supply, buy/sell volume, average buy price, and unrealized PnL.
  • Use as the top-level overview before drilling into Holder Positions for the exact wallets behind each label.
  • Provide a Solana token_address.
  • Use interval=1h for the volume fields returned in the profile.
  • Set ui_amount_mode=raw for raw token amounts or ui_amount_mode=scaled for Solana Token-2022 scaled UI amounts when the token supports scaled UI amount extension.
  • Set include_zero_balance=false when you only want wallets that still hold the token.
  • Read token, holder_summary, and tags together to connect market context with cohort behavior.
  • Use holder-profile as the first stop for token-holder risk review, then drill into holder-positions for wallet-level evidence.
  • Compare percent_of_supply across labels before trusting volume alone; small active cohorts can still control meaningful supply.
  • Watch for a high share of bundler, sniper, insider, or dev holdings when evaluating launch quality.
  • Treat smart-trader participation as one signal among several; validate it against liquidity, price action, and current holdings.
  • Solana only.
  • interval currently supports 1h.
  • Holder labels depend on available indexing and classification coverage.
  • Cohort summaries are not wallet-level evidence; use holder-positions when you need exact wallets.

Authorizations

X-API-KEY
string
header
required

API key for authentication

Headers

x-chain
enum<string>
default:solana

Solana network only.

Available options:
solana

Query Parameters

token_address
string
required

Token mint address

Example:

"J3Dhvhga7QwgLWUGn43caDJtaoUTkDLmiMGqstS2Dw8A"

interval
enum<string>
default:1h

Time interval for volume data. Default: 1h

Available options:
1h
ui_amount_mode
enum<string>
default:raw

Display mode for token amounts. Default: raw

Available options:
scaled,
raw
include_zero_balance
boolean
default:true

Include wallets that have traded the token but no longer hold it (zero balance). Default: true

Response

JSON object containing token holder profile summary

success
boolean
required

Whether the request succeeded.

data
object
required

Holder-profile payload for the requested token.