← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL TOP POOLS

GeckoTerminal Top-Pool Data: Null vs Zero - Handle Missing Fields Correctly

The top-pools schema marks valuation and reserve fields as nullable, and market cap is null for unverified tokens. Ranking without handling that misleads.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

In CoinGecko's top-pools-by-token-address schema, fdv_usd, market_cap_usd and reserve_in_usd are nullable; market_cap_usd is null for unverified tokens (GeckoTerminal may display FDV instead, which may not be accurate). Transactions (buys, sells, buyers, sellers) and volume_usd by window are not marked nullable, so zeros there are measured. The default sort is by 24h volume and liquidity. Rank pools only on fields you know, keep nulls as unknown and never substitute FDV for a null market cap silently.

Fields and what missing values mean

FieldNull / absent meansZero / empty means
reserve_in_usdUnknown reserve value—
market_cap_usdNull for unverified tokens—
fdv_usdUnknown—
transactions.h24—Zero: no trades
volume_usd.h24—Zero: no volume
Geckoterminal Top Pools: how to read each fieldGeckoterminal Top Pools: how to read each field: reserve_in_usd — Unknown reserve value; market_cap_usd — Null for unverified tokens; fdv_usd — Unknown; transactions.h24 — Zero: no trades; volume_usd.h24 — Zero: no volume.reserve_in_usdUnknown reserve valuemarket_cap_usdNull for unverified tokensfdv_usdUnknowntransactions.h24Zero: no tradesvolume_usd.h24Zero: no volume
Geckoterminal Top Pools: missing vs zero, field by field. Original ChartsPod editorial graphic.

Put GeckoTerminal Top-Pool Data next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Handling policy

Policy for this sourcePolicy for this source: Rank on known reserve only; Don't substitute FDV for null market cap; Zero txns = inactive pool; Note sort order used; Pages beyond 10 need higher plan (docs).POLICY FOR THIS SOURCERank on known reserve onlyDon't substitute FDV for null market capZero txns = inactive poolNote sort order usedPages beyond 10 need higher plan (docs)
Apply this policy to every geckoterminal top pools request. Original ChartsPod editorial graphic.

Illustrative: a dashboard filled null market caps with FDV. Unverified tokens with large unvested supply appeared far more valuable than their circulating market cap would suggest. Keeping null and showing 'unverified' was more honest.

Conclusion

Related: DEX Screener Market Cap vs FDV: Why the Numbers Can Match, Missing Crypto API Data: Null, Zero and Empty Arrays Mean Different Things.

Rank pools only on fields you know, keep nulls as unknown and never substitute FDV for a null market cap silently.

Review GeckoTerminal Top-Pool Data with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

Why is market_cap_usd null?

CoinGecko returns null for unverified tokens.

Which fields are nullable?

fdv_usd, market_cap_usd, reserve_in_usd and native-currency prices, per the schema.

Are transaction counts nullable?

Not marked nullable.

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.

  1. 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.