CoinPaprika
60,80311,599 active · 49,204 inactiveThe public catalog changes during the day. This site preserves the dated file value rather than presenting it as a live death count.
Official source ↗Coverage audit · 4 Aug 2026
The numbers below are not additive. Each source mixes different concepts—projects, assets, contracts, markets, wrappers and derivatives—and every “inactive” flag describes market support, not team communication.
CoinPaprika
60,80311,599 active · 49,204 inactiveThe public catalog changes during the day. This site preserves the dated file value rather than presenting it as a live death count.
Official source ↗CoinGecko
18,11118,111 activeThis snapshot contains active IDs only; inactive history and broader on-chain-asset marketing counts describe different cohorts.
Official source ↗CoinMarketCap
37,2948,180 active · 1,756 inactive · 27,358 untrackedActive, inactive and untracked are listing states. They do not establish the newest meaningful event from a project team.
Official source ↗CryptoRank
35,000provider-reported scaleThe displayed scale is provider-reported and can include asset types outside this site’s reviewed project model.
Official source ↗DropsTab
9,000provider-reported scaleThe displayed scale is provider-reported and was not imported into the reviewed project set.
Official source ↗Strongest structural conclusion
The production scope must be the union of standard provider listings successfully observed on a named date, canonicalized by chain and contract—not by symbol.
Adapter ledger
Credentials stay server-side. Access does not imply permission to republish: licensing must be cleared separately for each provider.
Inactive is a candidate signal, not a dead-project verdict.
Documentation ↗The Pro endpoint can request inactive supported coins; project metadata requires additional calls.
Documentation ↗The documented keyless API supplied 8,180 active, 1,756 inactive and 27,358 untracked IDs. V2 metadata can seed official-link candidates in 100-ID batches, but production publication still needs an applicable commercial plan; rows must be deduplicated by numeric ID, chain and contract.
Documentation ↗35,000+ is provider-reported, not an imported snapshot. Daily credits and rate limits constrain a full refresh.
Documentation ↗9,000+ is provider-reported, not an imported snapshot. No inventory is republished until access and reuse terms are confirmed.
Documentation ↗CoinMarketCap
The map endpoint distinguishes active, inactive and untracked listings. is_active=1 means at least one tracked market—not an active team. The info endpoint supplies official-link candidates but no last post, commit or website update.
Risk: commercial-use wording is internally inconsistent across current pricing materials. Obtain written confirmation before public redistribution.
Pricing and licensing FAQ ↗CoinGecko
The coins list exposes supported IDs; inactive status is paid-only. Coin detail supplies links and four-week aggregate developer data, not the exact newest meaningful commit. Its market last_updated field is not project-content freshness.
Risk: standard commercial plans require attribution and do not permit raw API redistribution; white-labelling needs Enterprise terms.
License explanation ↗CoinPaprika
The unauthenticated coin list yielded this snapshot’s 60,327 IDs. “Active” means current price and volume can be calculated. The deprecated Twitter endpoint is not suitable production infrastructure.
Risk: free use is non-commercial and attribution is mandatory; only Enterprise explicitly permits redistribution.
API terms ↗DropsTab
The coin endpoint can distinguish currently trading, not yet trading and no longer trading. The documented detailed schema does not promise official social or repository links.
Risk: the paid commercial API has no clear public redistribution/retention terms. Written permission is a launch dependency.
Terms of use ↗CryptoRank
The v3 profile can expose lifecycle plus website, GitHub, X and community-link candidates. “Inactive” is documented as not trading, not as a communication assessment.
Risk: pricing uses unclear license abbreviations. Confirm attribution, share-alike and retained-data rights in writing.
Terms and conditions ↗Primary evidence
Exact dates come from the source behind each door—and each source has a different blind spot.
A stable numeric account ID and native created_at can date posts. Standard timelines are bounded, handles can change, and private communication is invisible.
Default-branch commit timestamps are exact for that history. Other branches, moved repositories, private work, bots and backdated Git metadata can overturn the broader inference.
Commit API ↗Start content-hash monitoring now. HTTP Last-Modified, sitemap dates and Wayback captures usually cannot prove the exact historic edit time.
Only named, accessible forums, Telegram, Discord, governance and public AMAs can be scoped. Deleted messages, DMs and investor calls remain unknown.
See failure modes →