GeckoTerminal New-Pool Data: Null vs Zero - Handle Missing Fields Correctly
New pools arrive before most of their data does. Nulls are common in the first hours and should be read as 'not yet known'.
Short answer
CoinGecko's new-pools endpoints list recently created pools by network or across networks. For a pool minutes old, valuation and reserve fields may be null and transaction counts low or zero; token metadata may be incomplete. Treat nulls as not yet known, zeros as measured (no trades yet), and re-fetch after a delay before judging. Use pool_created_at to compute age and apply your new-pool due diligence regardless of how complete the data looks.
Fields and what missing values mean
| Field | Null / absent means | Zero / empty means |
|---|---|---|
| reserve_in_usd / fdv_usd | Not yet known | — |
| market_cap_usd | Null for unverified tokens | — |
| transactions | — | Zero: no trades yet |
| pool_created_at | Should be present | — |
| Token metadata | Incomplete early | — |
Put GeckoTerminal New-Pool Data next to price, flow and positioning in one workspace.
Open a ChartsPod workspaceHandling policy
Illustrative: a scanner skips new pools whose reserve_in_usd is null. Ten minutes later, half of them have reserves populated. A delayed second pass catches pools the first pass dropped.
Conclusion
Related: New DEX Pools: A Due-Diligence Checklist Before the First Trade, DEX Screener New Pairs: Filter Liquidity, Activity and Pool Age.
Use pool_created_at to compute age and apply your new-pool due diligence regardless of how complete the data looks.
Review GeckoTerminal New-Pool Data with bar replay before using it live.
Open ChartsPod replayQuestions readers ask
Why are new pools full of nulls?
Data populates over time after creation.
Should I skip pools with nulls?
Re-check later rather than dropping them.
How do I get pool age?
From pool_created_at.
Sources and methodology
Field definitions come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a schema was not visible in the documentation, this guide says so and describes defensive handling rather than asserting field behaviour.
- CoinGecko onchain API: New pools by network — recently created pools.
- CoinGecko onchain API: Top pools by token address (pool schema) — pool fields and nullability (fdv_usd, market_cap_usd, reserve_in_usd).
This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.
CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.