Skip to main content
GET
Token - First Buyers

Earliest buyer timeline for a token.

  • Buyers are ordered from earliest to latest.
  • position_status compares the wallet’s current holding to the amount it held right after its first buy.
  • buy_more means the wallet increased from its initial holding; hold means it kept the initial holding; sell_partial means it sold a meaningful portion; sell_all means it has almost fully exited.
  • page_summary aggregates position statuses for the buyers returned in the current page.
  • Wallet tags may include labels such as bundler, smart_trader, sniper, dev, insider, and kol.
  • 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.
  • Reconstruct the first wave of conviction behind a token by seeing who entered earliest, how much they bought, and what they did afterward.
  • Identify whether early buyers are still aligned with the token or already exited into later liquidity.
  • Surface suspicious launches where first buyers are heavily tagged as insiders, bundlers, snipers, KOLs, or other high-risk cohorts.
  • Build early-holder leaderboards that distinguish real conviction from fast extraction using current holding and position status.
  • Feed post-launch investigations, alpha research, and risk engines with the wallets that shaped the token’s first market structure.
  • Provide a Solana token_address.
  • Use offset and limit to page through the earliest buyers.
  • Start with the default limit=70, then page forward if you need more of the first-buyer cohort.
  • Read first_buy_volume, first_buy_volume_usd, initial_holding, and current_holding together to understand each wallet’s behavior.
  • Use position_status and tags to prioritize wallets worth deeper investigation.
  • Treat early buyers as a high-signal cohort, especially around new launches where first entries often shape the token’s market structure.
  • Combine position_status with wallet tags to distinguish conviction from coordinated extraction.
  • Use first-buyers before wallet-tags-tracker when you need to know which wallets seeded the earliest market activity.
  • Pair this endpoint with holder-positions to inspect current exposure and PnL for the wallets that entered first.
  • Solana only.
  • Pagination is limited to the first 1,000 buyers; offset + limit must not exceed 1,000.
  • limit defaults to 70 and supports up to 100 records per request.
  • position_status is relative to the wallet’s initial holding after its first buy, not to all-time maximum exposure.

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:

"So11111111111111111111111111111111111111112"

offset
integer
default:0

Pagination start position. Make sure offset + limit <= 1000.

Required range: 0 <= x <= 1000
limit
integer
default:70

Number of items per page. Make sure offset + limit <= 1000.

Required range: 1 <= x <= 100

Response

JSON object containing the first wallets that bought the token

success
boolean
required

Whether the request succeeded.

data
object
required