Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codex.io/llms.txt

Use this file to discover all available pages before exploring further.

Some fields on this endpoint (asset, assetDeployments, organization) are powered by The Grid and will only be populated for established, verified tokens. See Verified Metadata in the Discover Tokens recipe for full details.
Boolean filtering: The filters input supports an optional boolFilter field that accepts and, or, and not operators (nestable up to 4 levels). Use it when you need different filter conditions for a subsets of tokens, such as per-network thresholds, or across different fields. For example, you might want different filter conditions depending on whether tokens are on Solana or Base. See Advanced Filtering for details.

​
Returns

​
Arguments

​
Usage Guidelines

  • Response limit: 200 tokens per request
  • 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.

​
Troubleshooting Tips

We actually remove potential scam tokens automatically without this filter. If you set potentialScamto true, your results will show all (potentially) scam tokens that we have flagged. If set to false, it will return similar results as without the filter, however, all majors and stables will be included now. While false positives can occur, our detection system significantly reduces exposure to scam tokens.We also allow users to flag scams on our frontend at Defined.fi (moderated daily) which will update our API.
To filter for verified tokens, use isVerified: true in your filters input — this excludes tokens flagged as scams. To read verification status in the response, use isScam on the nested token object (e.g., token { isScam }). isScam: false is Codex’s equivalent of a token being “verified.” Note: there is no isVerified response field — it only works as a filter input.
Check if the token has been flagged as a potential scam by adding includeScams: true to your filters. Also verify you’re searching the correct network and the token has trading activity (we only index tokens after swaps have occurred).
Add quality filters to improve results. We recommend setting minimum thresholds for volume, liquidity, holders, etc. Additionally, rank results by trendingScore24 or volume24 rather than liquidity to get more meaningful results. Experiment with filters that will suit your needs.
Response times are generally 60-150ms and it takes ~2-5 seconds to update the search cluster with new data. Contact our team if you are experiencing consistently delayed response times.
A null or undefined value for Mintable/Freezable will both return null through Codex. To differentiate between the two, we’ve included an isMintableValid and isFreezableValid field to show whether the null value returned is trustworthy or if we simply lack that information for the token (ie: undefined).
Avoid sorting by createdAt when using phrase search. Instead, rank by trendingScore24 or volume24 — those produce far more meaningful results. We index over 75+ Million tokens, so finding the right token from a one-word phrase requires sensible ranking. For exact symbol matches, prefix the phrase with $ (e.g. $PEPE); for contract address matches, pass the address directly.
  • 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