Skip to main content
POST
POST /v1/token/security · 10 credits per 10 items The batch twin of Token Security - screen a whole watchlist in a single call. The response array is in input order with per-item {error} slots, and every item carries the same union shape (authorities, concentration, launch quality, holder profile, liquidity safety, taxes and honeypot, dexPaid, contract control on EVM, Token-2022 controls on Solana). Mixed EVM and Solana in one call is fine.
Authority tri-state: mintRevoked: true = renounced (safe), false = active, null = unknown. USDC keeps both authorities active (Circle can mint & freeze - expected for a regulated stablecoin, a red flag on a memecoin); BONK has both revoked.
Concentration, on EVM and Solana: top10HoldersPct, top25HoldersPct, top50HoldersPct, top100HoldersPct and top200HoldersPct are the shares of supply held by the largest holders. On EVM, with liquidity pools, burn wallets, CEX custody and launchpad lockers set aside, each is null when it cannot be measured exactly, never a partial sum. On Solana, they follow the rule of our token statistics (liquidity pools, the mint, burn wallets and the Pump.fun Mayhem agent set aside, then the price pool and known entities): a share can read low when many of the largest wallets are set aside, and all five are null for wrapped SOL and for the stablecoins and quote tokens kept out of wallet labels (USDC, USDT, USDG, EURC and similar). Same rules and figures as Token Security.
Launch quality, on EVM and Solana: snipersCount / snipersHoldingsPct are the wallets that bought in the first blocks after launch and still hold the token, and the share of supply they still hold from their launch buys; bundlersCount / bundlersHoldingsPct do the same for the bundlers: on EVM, wallets that bought at least twice within the launch window; on Solana, wallets that bought in a launch bundle (a buy transaction shared by several signing wallets in the token’s first slots, or the bundle of its creation). The creator counts in devHoldingsPct only. See Token Security.
Holder profile, on EVM and Solana: insidersCount / insidersHoldingsPct are the number of wallets linked to the token’s team or creator among the token’s main holders and the share of supply they hold; proTradersCount / proTradersHoldingsPct are the pro traders (wallets that have traded $50,000 or more through professional trading terminals) currently holding the token and the share of supply they hold. 0 means none detected, null means unknown. See Token Security.
Honeypot, contract control (renounced, isProxy, implementationAddress) and Token-2022 controls: same fields and meanings as Token Security. isHoneypot is null while it is unknown, on EVM and Solana alike: to exclude honeypots on both families, test isHoneypot !== true.
Batch: up to 100 items per call, across chains. Each item takes address or its other name, tokenAddress. lpBurnedPct, lpLockedPct and lpSource describe each token’s main market, named by poolAddress; for the LP of other pools, use the Pool Security batch.

Authorizations

Authorization
string
header
required

Your raw API key (not needed on the demo server).

Body

application/json
items
object[]
required

Up to 100 of {chain, address}, across chains. Response array is in input order with per-item {error} slots. Billed as one call (10 credits) per 10 tokens served. Each item takes address or its other name, tokenAddress.

Required array length: 1 - 100 elements
Example:

Response

200

Standard { data, meta } envelope.