Skip to main content
GET
Token - Wallet Tags Tracker

Three groupings under groups. They overlap each other — never sum one block into another.

  • tags — one series per tag. Overlapping: a dev+sniper wallet appears in both series, so summing these keys double-counts it.
  • tag_combinations — one series per exact tag set (dev, dev_sniper, dev_sniper_smart_trader, …). Disjoint: every wallet lands in exactly one key, so these are the only keys safe to sum for a total. Needs include_tag_combinations=true.
  • top_10_holder — a single series for the top 10 holders. An independent dimension that overlaps both tag blocks. Needs top_10_holder=true.

Reading the numbers. unix_time is the bucket open time. Volumes are gross and leg-based — a transaction that both buys and sells counts on both sides, with no netting. wallet_buy_count counts distinct wallets; tx_buy_count counts (wallet, transaction) pairs, so a bundle touching N wallets counts N times. Buckets with no activity are omitted from the series.

  • This endpoint consumes 30 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.
  • Follow the wallets that matter most — developers, snipers, smart traders, KOLs, and the token’s top holders — across every phase of a launch.
  • Build a launch-forensics timeline that reveals when insiders accumulated, when snipers rotated out, and when smart money started leaning in.
  • Separate signal from noise by comparing buy volume, sell volume, distinct wallet counts, and transaction intensity bucket by bucket.
  • Power monitoring dashboards, alerts, and post-launch research reports that show whether tagged wallets are holding conviction, taking profit, or exiting into liquidity.
  • Provide a token_address and a required time_from unix timestamp in seconds. Omit time_to to track activity up to now.
  • Pick time_frame by the question you’re asking: 1s30s for launch forensics, 1m30m for intraday rotation, 1h1M for trend.
  • Use tags=dev,sniper,smart_trader,kol to narrow the cohorts returned, or omit tags to return all supported tag series.
  • Set top_10_holder=true to add the top-holder series, and include_tag_combinations=true to add the disjoint cohorts.
  • While has_more is true, pass next_time_from back as time_from to page forward.
  • Start with a coarse interval to understand the overall story, then zoom into minute or second buckets around the suspicious launch, pump, or exit.
  • Score wallets from tag_combinations, not tags — any model that sums the tags keys will over-weight multi-tagged wallets.
  • Compare buy-side and sell-side wallet counts against USD volume to distinguish broad participation from a few large actors.
  • Pair this endpoint with price, volume, first-buyers, and holder-profile data to explain not just what happened, but who drove it.
  • Solana only. Supported tags are dev, sniper, smart_trader, and kol.
  • Supported tags are dev, sniper, smart_trader, and kol.
  • Maximum range per interval — seconds: 30 days, minutes: 60 days, hours: 90 days, 1D/1W/1M: 365 days. Exceeding it returns 400.
  • Some highly held or high-cost tokens (wSOL, USDC, USDT, BONK) are not supported for this endpoint.

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:

"9cRCn9rGT8V2imeM2BaKs13yhMEais3ruM3rPvTGpump"

time_from
integer
required

Start of the range, as a unix timestamp in seconds.

Example:

1782864000

time_to
integer

End of the range, as a unix timestamp in seconds. Defaults to now. Must be greater than time_from, and within the time_frame's maximum range.

Example:

1785369600

time_frame
enum<string>
default:1D

Size of each time bucket.

Available options:
1s,
5s,
15s,
30s,
1m,
3m,
5m,
15m,
30m,
1h,
2h,
4h,
1D,
1W,
1M
tags
enum<string>[]

Comma-separated wallet tags to restrict the response to. Defaults to all supported tags. Also narrows which keys appear in tag_combinations.

Available options:
dev,
sniper,
smart_trader,
kol
Example:
top_10_holder
boolean
default:false

Set to true to include the top_10_holder series.

include_tag_combinations
boolean
default:false

Set to true to include the tag_combinations block, the only block whose keys are safe to sum.

Response

JSON object containing tagged-wallet trading activity bucketed by interval, grouped by tag, by exact tag combination, and by top 10 holder

success
boolean
required

Whether the request succeeded.

data
object
required