bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
2.9 KiB
2.9 KiB
CoinGecko API: No Push for Liquidity — How Pool Data Gets to CoinGecko
Last Updated: 2026-02-20
Status: Reference
Summary
CoinGecko does not provide an API to push or submit liquidity pool data. Their API is read-only: you query price and pool data that they have already indexed. You cannot “push” cUSDT/cUSDC pool information to CoinGecko via API.
How CoinGecko Gets Liquidity Data
| Source | How it works |
|---|---|
| Supported chains (Ethereum, BSC, Polygon, etc.) | GeckoTerminal (CoinGecko’s indexer) automatically indexes DEX pools on-chain. Pools that exist on supported networks and DEXes (Uniswap, etc.) are discovered and updated from the blockchain — no API push. |
| Custom / unsupported chains (e.g. Chain 138) | Not indexed automatically. You must submit the chain/token via CoinGecko’s listing form and, when they support it, provide an API URL (e.g. GET /api/v1/report/coingecko?chainId=138) so they can pull data from your Token Aggregation Service. |
So:
- Chains CoinGecko “typically reviews” (Ethereum, BSC, Polygon, Base, etc.):
Pool data is pulled from chain by GeckoTerminal. You do not push it via API. You only need tokens listed (if not already) and liquidity on DEXes they already index. - Chain 138 (and other unsupported chains):
You submit the chain/tokens and give CoinGecko your report API URL; they then pull from your API. Still no “push” — they fetch from the URL you provide.
What You Can Do
For chains CoinGecko already supports (Ethereum, BSC, Polygon, etc.)
- List cUSDT/cUSDC on CoinGecko for that chain (via Submit coin if not already listed).
- Create liquidity pools on DEXes that GeckoTerminal indexes (e.g. Uniswap, SushiSwap, etc.) on that chain.
- CoinGecko/GeckoTerminal will automatically pick up those pools from on-chain data. No API push.
For Chain 138 (Defi Oracle Meta Mainnet)
- Submit the chain and tokens via CoinGecko’s listing process.
- Provide your report API URL (e.g.
https://<your-api>/api/v1/report/coingecko?chainId=138) so CoinGecko can pull token and liquidity data from your Token Aggregation Service. - Ensure
GET /api/v1/report/coingecko?chainId=138is public and returns the format described in CMC_COINGECKO_REPORTING.md.
References
- Token Aggregation report API:
smom-dbis-138/services/token-aggregation/docs/COINGECKO_SUBMISSION.md - Report format (tokens + liquidity_pools):
smom-dbis-138/services/token-aggregation/docs/CMC_COINGECKO_REPORTING.md - CoinGecko on-chain (read-only) API: CoinGecko Docs – Get On-chain Data
- GeckoTerminal: Indexes supported networks and DEXes from chain; no push API.