← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · GECKOTERMINAL TOP POOLS HISTORY

GeckoTerminal Top-Pool Data: History Limits - Avoid Silent Gaps

Top-pool lists return 20 pools per page, and paging beyond 10 pages needs a higher plan. Deep lists can be cut off without obvious errors.

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

Short answer

CoinGecko's top-pools-by-token endpoint returns up to 20 pools per page; paging beyond 10 pages requires the Analyst plan or above. Responses are cached (30 s paid, 60 s demo) and sorted by a chosen rule. There's no history of past rankings. For tokens with many pools, check whether you reached the paging limit, store snapshots with retrieval times and sort rule, and compare by pool address.

Documented limits

LimitValueEffect
Pools per page20Pagination
Pages without Analyst≤ 10≤ 200 pools
Cache30 s / 60 sSnapshot age
HistoryNot providedStore snapshots

Compare GeckoTerminal Top-Pool Data across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Where silent gaps come from

  • Paging limit reached silently
  • Snapshots without sort rule
  • Comparing by rank
  • Cache age ignored
Geckoterminal Top Pools: gap-safe collectionGeckoterminal Top Pools: gap-safe collection. Steps: 1. Page — 1 … n; 2. Detect limit — Page 10 full?; 3. Store — Snapshot + sort; 4. Compare — By address; 5. Log — Truncation1Page1 … n2Detect limitPage 10 full?3StoreSnapshot + sort4CompareBy address5LogTruncation
Make every gap explicit. Original ChartsPod editorial graphic.

Example

Geckoterminal Top Pools: a silent gap (illustrative)Geckoterminal Top Pools: a silent gap (illustrative): PAGES 1–10: 200 pools; PAGE 11: Requires higher plan; ANALYSIS: 'Token has 200 pools'; REALITY: More exist.PAGES 1–10200 poolsPAGE 11Requires higher planANALYSIS'Token has 200 pools'REALITYMore exist
Nothing in the data said it was missing. Original ChartsPod editorial graphic.

Illustrative: a token with hundreds of small pools appeared to have exactly 200 — the paging limit.

Related: GeckoTerminal Top-Pool Data: Event Time vs Retrieval Time, GeckoTerminal New-Pool Data: History Limits - Avoid Silent Gaps.

For tokens with many pools, check whether you reached the paging limit, store snapshots with retrieval times and sort rule, and compare by pool address.

Check GeckoTerminal Top-Pool Data against a live market before relying on it.

Try it in ChartsPod

Questions readers ask

How many pools per page?

Up to 20.

Is there a paging limit?

Beyond 10 pages needs the Analyst plan.

Is ranking history available?

No; store snapshots.

Sources and methodology

Limits come from DEX Screener's API reference, CoinGecko's onchain API documentation and Binance's Spot API documentation, read 17 October 2026. Where a limit isn't documented, this guide says so. Examples are illustrative.

  1. CoinGecko API: Top pools by token — 20 per page; >10 pages needs Analyst plan.

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.