filterTokens

​

Use this data for

• Token screeners and trending feeds. Rank by volume24, change24, trendingScore24, or any of 100+ ranking attributes to power gainer boards and new-listing feeds, scoped to one network or every network at once. Narrow further by specific exchanges or specific launchpads.
• Quality filtering for legit tokens. Combine profanity: false, potentialScam: false, and trendingIgnored: false with sensible liquidity and volume thresholds to surface real tokens and filter out scams, low-effort copies, stablecoins, and base assets.
• Category-scoped screens. Use the categories filter (TokenCategoryFilter) with anyOf, allOf, noneOf, and hasCategory to scope any screen to curated token categories like DeFi, L1, AI, and memes. Browse the available categories with categories.
• Launchpad (memescope) filtering. Filter by launchpadProtocol, launchpadCompleted, launchpadMigrated, and migration timestamps to surface graduating tokens (Pump.fun, Bonk, Meteora DBC) the moment they hit the open market. For live-streamed launchpad data, combine with our onLaunchpadTokenEventBatch subscription.
• Global fee data. Filter and sort on the full Global Fees Paid surface (totalFees{w}, feeToVolumeRatio{w}, poolFees24, builder tips, and more) to identify low-friction trading pairs or tokens where MEV dominates. See Global Fees Paid for the full field map.
• Holder-quality and bot-detection screens. Use top10HoldersPercent, insiderHeldPercentage, bundlerHeldPercentage, sniperHeldPercentage, and walletAgeAvg to filter out concentrated supplies and bot-driven launches. See Snipers, bundlers, and insiders for how these holders are labelled.

​

Example

{
  filterTokens(
    filters: {network: 1399811149, buyVolume24: {gt: 5000}, circulatingMarketCap: {gt: 1000000, lt: 20000000}}
    rankings: [{attribute: trendingScore24, direction: DESC}]
    limit: 25
  ) {
    results {
      buyVolume24
      sellVolume24
      circulatingMarketCap
      createdAt
      holders
      liquidity
      token {
        info {
          address
          name
          symbol
        }
        createdAt
        creatorAddress
        createTransactionHash
      }
      txnCount24
      walletAgeAvg
      walletAgeStd
    }
  }
}

​

Usage Guidelines

• Response limit: 200 tokens per request
• If rankings is omitted, results default to trending order (the trendingScore attribute). Pass rankings explicitly when you need a specific sort.
• Use trendingScore24 or volume24 rankings for better results instead of createdAt
• Apply quality filters such as volume and liquidity minimums to avoid low quality tokens
• Use phrase parameter for searching by token name, symbol, or contract address
• For exact symbol searches, use the $ prefix and combine phrase with volume/liquidity rankings to improve results
• We recommend the use of useAggregatedStats: true to include aggregated token stats in results. This is not enabled by default. By default, volume, transaction and liquidity stats come from the token’s top pair only, so tokens that share a pool (for example SOL and USDC) can show the same values. With useAggregatedStats: true stats are aggregated across all of the token’s pairs and pair is null. The two modes return different liquidity and totalLiquidityUsd values, so don’t mix them in one view.
• Without useAggregatedStats, pair, liquidity, volume24 and priceUSD come from the token’s top pair: the pool with the highest combined score for volume, liquidity, activity and recency. It is not always the deepest pool, and it can switch as trading shifts, in which case all of those fields switch together. Use liquidPair and liquidPairLiquidity for the deepest pool.
• trendingIgnored: false leaves out tokens that aren’t interesting for trending. A token is flagged when it is on a fixed list of base assets and liquid staking tokens, when a moderator excluded it, when its risk verdict is HIGH_RISK or SCAM, or when its price has barely moved (every window from 5m to 24h within about 3%). Because of the last rule it is not a fixed “majors” list: a stablecoin or staking token that isn’t on the fixed list can lose the flag on a volatile day.
• Use creatorAddresses in filters to list the tokens a set of wallets created (up to 25 addresses).
• Use socials and media in filters to match tokens by their links and images. Each takes hasAny, anyOf, allOf and noneOf, over TokenSocialLink values (such as TWITTER, TELEGRAM, WEBSITE) or TokenMediaType values (LOGO, BANNER, VIDEO). For example, media: { anyOf: [LOGO] } keeps only tokens with a logo. Grid organization links and images are not counted.
• To get stats for tokens you already know, pass them in the top-level tokens argument as address:networkId strings, for example filterTokens(tokens: ["So11111111111111111111111111111111111111112:1399811149", "TOKEN_ADDRESS:8453"]). tokens is an argument of filterTokens, not a field inside filters, and takes strings, not objects. It accepts up to 200 IDs (excludeTokens too). All requested tokens are returned without raising limit, and IDs that are not indexed are left out without an error.

​

Troubleshooting Tips

​

Related Recipes

• Discover Tokens: Build token discovery pages with trending data, filters, and search
• Launchpads: Build a launchpad discovery view with real-time token lifecycle updates
• Launchpad Lifecycle: Understand how tokens progress through launchpad stages from bonding curve to graduation