Filter Tokens logo

Catalog action Blockchain Data

Discover and filter tokens across blockchain networks using the Codex (Defined.fi) API. Returns ranked token lists with price, volume, liquidity, market cap, holder counts, and buy/sell activity. Supports filtering by network, minimum liquidity, volume thresholds, and scam exclusion. Ideal for: finding trending tokens, screening new launches, monitoring trading activity on specific chains.

At a Glance

FieldValue
Action IDcodex-filter-tokens
CategoryBlockchain Data
ConnectorNot required
Requires gasNo
Funds movementNone declared
Tagsonchain, blockchain, token, trending, filter, analytics, read

Payload Schema

FieldTypeRequiredDescription
networkIdnumberNoNetwork ID to filter tokens on. Common values: 1 (Ethereum), 8453 (Base), 137 (Polygon), 42161 (Arbitrum), 10 (Optimism). Default: 8453 (Base)
minLiquiditynumberNoMinimum liquidity in USD. Filters out low-liquidity tokens. Default: 10000
minVolume24numberNoMinimum 24-hour trading volume in USD. Default: 5000
excludeScamsbooleanNoExclude tokens flagged as potential scams. Default: true
excludeStablecoinsbooleanNoExclude stablecoins and wrapped tokens from results using Codex trendingIgnored flag. Default: true
rankBystringNoAttribute to rank tokens by. Options: trendingScore24 (24h trending), trendingScore1 (1h trending), volume24, change24, liquidity, marketCap, holders, createdAt. Default: trendingScore24
rankDirectionstringNoSort direction for ranking. Default: DESC
limitnumberNoMaximum number of tokens to return. Range: 1-200. Default: 50
offsetnumberNoNumber of tokens to skip for pagination. Default: 0

Result Schema

FieldTypeRequiredDescription
countnumberYesTotal number of tokens matching the filter criteria
pagenumberYesCurrent page number
tokensarrayYesList of tokens matching the filter criteria

Examples

json
{ "type": "codex-filter-tokens", "payload": { "networkId": 8453, "minLiquidity": 10000, "minVolume24": 5000, "excludeScams": true, "excludeStablecoins": true }, "children": []}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.

Ask a question... ⌘I