When scanning a token on Ethereum, Base, or BNB Smart Chain, the results.advanced object contains the following indicators.

Honeypot Detection

Field	Type	Description
`honeypot.score`	integer	Honeypot risk from 0 (safe) to 100 (confirmed honeypot)
`honeypot.message`	string	Explanation of the honeypot finding

A honeypot is a token that can be bought but cannot be sold. This is typically achieved through malicious contract logic that blocks or taxes sell transactions.

Score	Meaning
0	No honeypot detected
50	Potential honeypot -- inconclusive simulation
100	Confirmed honeypot -- sell transactions are blocked

Contract Verification

Field	Type	Description
`verified`	boolean	`true` if the contract source code is verified on the block explorer. Unverified contracts are a major red flag -- the simple score drops to 10.

Ownership & Control

Field	Type	Description
`renounced`	boolean	`true` if contract ownership has been renounced. A non-renounced contract can have its behaviour changed by the owner.
`owner_address`	string or null	Current contract owner address. `null` if ownership is renounced.
`take_back_ownership`	boolean	`true` if the contract contains a function to reclaim ownership after renouncing
`hidden_owners`	boolean	`true` if the contract uses techniques to hide the real owner
`proxy_contract`	boolean	`true` if the contract is upgradeable via a proxy pattern -- the implementation can be swapped at any time

Trading Restrictions

Field	Type	Description
`pausable`	boolean	`true` if trading can be paused by the owner
`cannot_buy`	boolean	`true` if buy transactions are currently blocked
`cannot_sell_all`	boolean	`true` if holders are prevented from selling their entire balance
`anti_whale`	boolean	`true` if there are maximum transaction or holding limits
`anti_whale_modifiable`	boolean	`true` if the anti-whale thresholds can be changed by the owner
`limit_trades_over_time`	boolean	`true` if there are cooldown periods between trades
`has_whitelist`	boolean	`true` if the contract has a whitelist mechanism (only approved addresses can trade)
`has_blacklist`	boolean	`true` if the contract has a blacklist mechanism (specific addresses can be blocked from trading)

Tax

Field	Type	Description
`tax.buy`	number	Buy tax percentage (e.g. `5` means 5%)
`tax.sell`	number	Sell tax percentage
`tax.transfer`	number	Transfer tax percentage
`tax_modifiable`	boolean	`true` if the owner can change tax rates after deployment
`modify_tax_for_individuals`	boolean	`true` if different tax rates can be set per address

Minting

Field	Type	Description
`mintable`	boolean	`true` if new tokens can be minted, inflating supply

Advanced Contract Risks

Field	Type	Description
`make_external_calls`	boolean	`true` if the contract makes external calls that could be exploited
`can_selfdestruct_contract`	boolean	`true` if the contract contains a self-destruct function
`change_balance_off_chain`	boolean	`true` if token balances can be manipulated without on-chain transactions
`gas_abuse`	boolean	`true` if the contract contains gas manipulation that could grief transactions
`known_honeypot_creator`	boolean	`true` if the deployer address has previously created confirmed honeypot tokens

Creator

Field	Type	Description
`creator.address`	string or null	Address that deployed the token contract
`creator.balance`	number	Creator's current token balance

Liquidity

Field	Type	Description
`locked_liquidity`	array	List of liquidity pools and their lock status
`locked_liquidity_weighted`	number	Volume-weighted average of locked liquidity across all pools (0-100)

Each entry in the locked_liquidity array:

Field	Type	Description
`pair_address`	string or null	LP pair address
`dex`	string	DEX name (e.g. `"uniswap"`, `"pancakeswap"`)
`total_locked`	number	Percentage of LP tokens locked (0-100)
`locks`	array	Individual lock details
`locks[].percentage`	number	Percentage in this lock
`locks[].type`	string	`"burn"` (permanently locked) or `"vested"` (time-locked)
`locks[].unlock_time`	integer	Unix timestamp when the lock expires (for vested locks)

Top Holders

Field	Type	Description
`holder_count`	integer	Total number of token holders
`top_holders`	array	Top 20 holders by balance

Each holder entry:

Field	Type	Description
`address`	string	Wallet address
`balance`	number	Token balance
`percentage`	number	Percentage of total supply
`is_contract`	boolean	Whether this address is a smart contract

Multichain Tokens

Some tokens exist across multiple EVM chains. When detected, the response includes:

Field	Type	Description
`multichain`	array	List of chain IDs where this token exists
`multichain_top_holders`	array	Top holders aggregated across all chains

Each multichain holder entry:

Field	Type	Description
`address`	string	Wallet address
`total_balance`	number	Combined balance across all chains
`total_percentage`	number	Combined percentage of total supply
`balances`	array	Per-chain breakdown with `balance`, `percentage`, and `chain`