Wallet tags are returned through the
identity object. A wallet can have multiple tags at once, so always read identity.tags as an array instead of assuming one label.Quick Start
Wallet identity appears across PnL V2 wallet, token, leaderboard, and batch responses when a label is known.
identity can be null.
identity.type is the primary tag for single-badge UIs. identity.tags is the complete tag list and should be used when you need every label.
In the example above, the wallet is labeled as a known bot. A UI could show one badge from identity.type, while a filtering system should read every value in identity.tags.
Raw Wallet Signals
Some wallet endpoints also return a rawtags object with lower-level arbitrage and platform signals:
identity.tags for UI labels and filtering logic. Use the raw tags object when you specifically need the underlying arbitrage/platform signals.
Supported Wallet Tags
axiom-flash is accepted as a platform query value, but identity responses normalize it to the axiom tag.Tag Categories
People and Bots
Usekol, bot, potential_bot, and arbitrage to separate human traders from automated or MEV-style behavior.
potential_bot is a softer heuristic signal. bot and arbitrage are stronger curated labels.
Safety and Infrastructure
Usehacker, spam_dusting, and exchange for safety warnings and infrastructure labels.
These tags are curated and may also promote a readable label into identity.name, for example an exchange name or spam-dusting label.
Token Context
Usedeveloper and pool on token-scoped endpoints to find token creators, pool deployers, mint authorities, LP accounts, pool vaults, and bonding curve accounts.
Token-scoped endpoints resolve these roles for the token in the URL, which is useful for detecting insiders and non-trader wallets in token holder or first-buyer lists.
Platform Filters
The endpoints below acceptplatform=axiom, platform=bloom, platform=photon, or comma-separated combinations.

GET /v2/pnl/leaderboard/topGET /v2/pnl/tokens/:token/tradersGET /v2/pnl/tokens/:token/first-buyers
platform=axiom-flash is also accepted and is treated as axiom.
Where Tags Appear
Wallet identity is returned on PnL V2 wallet, token, leaderboard, and batch responses when the API can resolve a label.- Wallet summary and wallet positions return top-level
identity. - Token trader endpoints return
identityper trader. - Token-scoped endpoints resolve
developerandpoolfor the token in the URL. - Position batch endpoints return
identityper wallet or position. POST /v2/pnl/wallets/batchreturns bothidentityand rawtagsper wallet.
Common Use Cases
FAQ
What is the difference between bot, potential_bot, and arbitrage?
What is the difference between bot, potential_bot, and arbitrage?
bot is a curated named bot label. potential_bot is a softer heuristic signal from wallet behavior. arbitrage is a confirmed MEV or arbitrage wallet label.Why does axiom-flash become axiom?
Why does axiom-flash become axiom?
axiom-flash is accepted for platform filtering, but identity responses normalize platform aliases so clients only need to handle the canonical axiom tag.How does SNS interact with other labels?
How does SNS interact with other labels?
SNS adds
identity.sns.domain and the sns tag when a primary .sol domain exists. Curated labels keep identity.name; SNS is attached in parallel (for example tags: ["kol", "sns"]). See SNS Primary Domain.