For the complete documentation index, see llms.txt. This page is also available as Markdown.

Methodology

How every Investor Intel figure is made: where it comes from, how often it is captured, which clock and units it uses, and how our own calculations are built. The same page is in the app under Help, then How it works and terms, at the foot of the sidebar (/intel/methodology), and every receipt and figure footnote links to the part that explains it.

How often each figure is captured

Every figure is read from a scheduled capture, a shared cache of dated provider pages, or your own records. Opening a page never asks a provider for a figure that a capture already holds. A figure is called stale once it is older than one and a half times its capture interval plus fifteen minutes: one missed run is tolerated, two are not. Each page's capture receipts show when its lanes actually ran.

This table is generated from the same registry the hosted MCP server publishes in tools/list, so the app, the agents and this page agree.

What
When (UTC)
Stale after
Source
Store

Asset catalogue: price, market cap, volume and rank for every listed asset

Every 5 minutes; the deeper pages at :25 and :55

23 min

coinmarketcap, coingecko

market_assets

Retained price observations behind charts and quotes

Every minute

17 min

coinmarketcap

intel_quote_tape, intel_market_observations

Candles for one asset, from the stored archive, the shared candle caches and retained prices

Built when read, from stored data only; a series is as fresh as its newest completed candle

One and a half candle widths plus fifteen minutes

binance, coinbase, kraken, kucoin, coinmarketcap, coingecko

market_asset_candles, exchange_market_response_cache, market_data_response_cache, intel_quote_tape

Liquidations across derivatives venues

Every 5 minutes

23 min

coinmarketcap

intel_liquidation_snapshots

Market regime: total market cap, dominance, fear and greed, altcoin season

Hourly at :07

105 min

coinmarketcap

intel_regime_snapshots

CMC 20 and CMC 100 index constituents

Hourly at :07

105 min

coinmarketcap

intel_index_constituent_snapshots

Trending and top-gainer list membership

Hourly at :07

105 min

coinmarketcap

intel_attention_snapshots

Category totals

Hourly at :17; category members daily from 01:35

105 min

coinmarketcap

intel_category_snapshots

Each asset's move ranked against its own history

Hourly at :52

105 min

investor_intel

intel_unusual_move_scores

Derivatives open interest, funding and basis by venue

Hourly at :13; each asset asked about every 2 hours

3 h 15 min

coinmarketcap

intel_derivatives_board_captures, intel_derivatives_board_snapshots

Spot exchange rankings by reported volume

Hourly at :14

105 min

coinmarketcap

market_data_response_cache

Largest pairs of the tracked exchanges

Every 6 hours at 01:26, 07:26, 13:26 and 19:26

9 h 15 min

coinmarketcap

market_data_response_cache

Daily volume history of the tracked exchanges

Daily at 05:08

36 h 15 min

coinmarketcap

market_data_response_cache

Where each tracked asset trades (market pairs)

Every 30 minutes at :06 and :36

60 min

coinmarketcap

market_data_response_cache

Daily rank history (end-of-day listing)

Daily at 00:20 for the day before

36 h 15 min

coinmarketcap

intel_rank_history

Dated all-time highs and lows, period opens and closes

Daily at 02:49

36 h 15 min

coinmarketcap

intel_asset_performance_stats

Exchange reserves

Daily at 04:50

36 h 15 min

coinmarketcap

intel_exchange_reserve_snapshots

Venue share of spot and derivatives volume

Daily at 04:55

36 h 15 min

coinmarketcap

intel_venue_share_snapshots

CoinMarketCap categories against our sector labels

Daily at 04:08

36 h 15 min

investor_intel

intel_sector_source_daily

Airdrop calendar

Daily at 05:30

36 h 15 min

coinmarketcap

intel_airdrop_snapshots

New listings and their security inspection

Daily at 06:10

36 h 15 min

coinmarketcap

intel_new_listing_snapshots

Whether CoinMarketCap and an independent source agree

Hourly at :28

105 min

investor_intel

intel_source_agreement_runs

Dated end-of-day listings since 28 April 2013 (rank atlas, backtest, history atlas)

Kept warm in the shared cache: the daily regime atlas every 2 hours and the rank atlas dates every 6 hours; any other page when a member opens it. A past day never changes, and each page is kept 7 days

Never: a past day does not change

coinmarketcap

market_data_response_cache

Blockchain network statistics

Not captured on the current CoinMarketCap plan

Not captured

coinmarketcap

intel_network_stats_snapshots

Launchpad stages from CoinMarketCap (Pump.fun, Four.meme)

Every 5 minutes, and when a member opens the graduation board

23 min

coinmarketcap

intel_meme_stage_snapshots

Launchpad stages from CoinGecko onchain

Hourly at :41

105 min

coingecko

intel_meme_stage_snapshots

SunPump launches read off TRON

Hourly at :43

105 min

trongrid

intel_meme_stage_snapshots

DEX trending, new and gainer boards per network

Hourly at :49

105 min

coinmarketcap

intel_dex_board_captures

Token security for one contract: holders, developer, mint, freeze, LP and tax

When a member opens the token page, at most once a day per token

36 h 15 min

birdeye, coingecko, solana_rpc, coinmarketcap

token_security_snapshots, token_risk_scores

Exit quote: what selling a token now would move and return

Quoted live when asked and never stored; every agent quote counts toward a daily cap per member

Read live

dflow, birdeye, alchemy, four_meme, pancakeswap, uniswap

none (not stored)

Holder tags and cohorts per tracked contract

Hourly at :38

105 min

coinmarketcap

intel_holder_intel_contracts

Memecoin board rows (only rows refreshed in the last 6 hours are shown)

Continuously refreshed; rows older than 6 hours are left out

9 h 15 min

dexscreener, birdeye

memecoin_latest_tokens

Tokenized real-world asset universe by type

Hourly at :07

105 min

coinmarketcap

intel_rwa_universe_snapshots

Where tokenized assets trade (pairs and pools)

Every 30 minutes at :21 and :51

60 min

coinmarketcap

market_data_response_cache

Wrapper prices against their anchor (premiums)

Every 2 hours at :47 on even hours

3 h 15 min

coinmarketcap, chainlink

intel_rwa_wrapper_assets

Advertised and realised yield from NAV feeds

Every 6 hours at 01:29, 07:29, 13:29 and 19:29

9 h 15 min

chainlink, issuers

intel_rwa_yield_snapshots

Issuer identity, filings and holder concentration

Daily at 02:19, holder concentration at 02:53

36 h 15 min

sec, gleif, coinmarketcap

intel_rwa_issuer_filings

RWA coverage headline and daily changes

Daily at 03:19, after the asset map at 03:11

36 h 15 min

coinmarketcap

intel_rwa_coverage_assets

On-chain pool depth per tokenized asset token

Daily at 03:34

36 h 15 min

coinmarketcap

intel_rwa_depth_snapshots

SEC filer facts for the company under a tokenized stock

Daily at 03:47

36 h 15 min

sec

intel_rwa_underlying_registrants

Issuer terms (who may redeem, minimums, hours)

Reviewed by hand; a review has a date and no expiry

Not by age: a review has a date, never an expiry

issuers

intel_market_observations

Your own watchlists, alerts, notes, proposals and call budget

Read live on every request

Read live

investor_intel

member tables

One clock, its zone always named

Every time is shown in your own time zone with the zone written beside it (14:05 CDT). Data days in pickers, tables and charts are UTC days, the days our captures and providers close on; a day is published once it has closed in UTC, so the newest dated listing is yesterday's. Capture schedules are given in UTC.

You can read every time in UTC instead, in Settings under Display. Each time then says UTC, so a time is never shown without its zone. The choice is kept in your browser and written to your profile, so alerts and briefs sent to you by email or Telegram use the same clock (UTC when we do not know your zone). Shared documents such as a fund's board brief keep UTC.

Observed is when the provider measured the figure. Captured is when our lane stored it. Retrieved is when a read was answered. They are different facts and are shown separately when they differ. A capture filed under an hour (a capture window) is never shown as the time the figure was true.

Units

  • Amounts are stored in US dollars. A display currency converts only the figures Settings lists, at the newest hourly rate; everything else says it is in USD. Past days are never converted at today's rate.

  • Percent changes are simple returns over the stated window. A basis point (bps) is 0.01 percent. Dominance is a share of total market capitalisation as the provider publishes it; a dominance of 0 means not published, never zero.

  • Funding is shown as a percent per the venue's own funding period. The provider sends a fraction per period (0.0001 is 0.0100%). Periods differ by venue (eight hours on some, one hour on others) and are not sent, so rates are not annualised and are not directly comparable across venues. Basis is the provider's index basis, as a percent of the index.

Ranking

  • Markets is ordered by CoinMarketCap's own market-cap rank, not by sorting raw market caps. A market cap more than 10% above the smallest cap ranked ahead of it is flagged, shown with a note and left out of market totals, because the provider's ranking does not count it.

  • "From recorded high" is the distance from the highest price we have recorded since the date shown. The all-time high column is CoinMarketCap's dated all-time high. They are different figures and are labelled as such.

Derivatives

  • For each asset we read one batch of up to 250 derivative contracts across venues: the same request for the asset page, the leverage concentration view and the market structure tables, so all three count the same contracts. The latest whole batch is evaluated at the time it was fetched and its age is printed.

  • A contract last updated more than one hour before the batch was fetched is stale: shown, and left out of totals. A venue whose open interest is under 0.2% of its volume, or whose exchange score is under 3 out of 10, is flagged as implausible and left out. A contract listed twice is counted once.

  • Deribit options and CME futures are not in our licensed source. CoinMarketCap lists no CME contracts, and lists Deribit only through two USDC-margined perpetuals whose open interest does not reflect Deribit's inverse contracts or its options (checked 2026-10-24). We leave them out rather than estimate them, so every open interest share is a share of the venues CoinMarketCap covers, not of the whole market.

  • The default derivatives view is Leverage concentration (/intel/derivatives), linked from the sidebar and every asset page.

Screen backtest

  • On each formation date the cohort is every asset in the end-of-day listing of that date that passed the screen (rank band and optional bounds), best rank first, at most 100. Assets that were later delisted are in it exactly as they were that day. Its return is read from the listing one step later.

  • An asset missing from the exit date's listing to rank 1,000 has no observed exit. It stays in the cohort: the observed mean uses the exits we saw, and the worst case counts every unobserved exit as a total loss. The truth lies between the two. Members are equal weight. The whole rank band of the same date (equal weight) and BTC are shown beside each period.

  • The headline compounds the period means in order. A period whose screen matched nothing held cash at 0%. A period that could not be read is left out of the chain, and the headline says how many periods were read.

  • Stablecoins can be left out. They are identified by the provider's stablecoin tags or, on a row without tags, by a fixed list of dollar and euro stablecoin symbols. The rank-band benchmark leaves them out too.

  • A trading cost you enter is charged on turnover: at each formation date on the share of the cohort bought, and at the next on the share sold. Re-weighting members that stay is not charged and there is no slippage model.

  • A period with fewer than 10 members, or a run with fewer than 30 observed exits, is marked as a small sample.

  • Downloads: the period file holds our calculations only; the member file holds each member's rank, identifier and return, and CoinMarketCap's entry and exit prices are left blank unless the data licence allows export. A saved screen stores the screen, not its prices, and is replayed when opened.

Rank atlas

  • The rank atlas reads CoinMarketCap's end-of-day listing, to a depth of 100, on sampled dates since 28 April 2013: every six months since 2013, every three months over five years and every month over two years by default, or every month over any period. Each sampled date is one shared page, kept seven days.

  • For each step between two sampled dates it lists who entered and who left the top 10, 25, 50 or 100, and how many former members are not in the top 100 today. "Took the place of" pairs each entrant with the leaver whose previous rank was closest; it is a reading aid, not a cause.

  • The table download holds every sampled date's top N: date, rank, identifier, symbol and name. No prices.

Receipts and sources

  • A source call receipt names the provider, the endpoint and parameters, whether a live call or a shared copy answered, the credits it cost, the HTTP status, the times it was observed, captured and retrieved, and the command to reproduce the call with your own key. A capture receipt does the same for the scheduled run behind a stored figure. Reading a receipt makes no provider call.

  • Fresh means a provider call answered this read. Cached means a shared copy inside its refresh limit. Stale means past its refresh limit. Unavailable means nothing usable answered, which is never shown as an empty market.

  • A figure we calculate (a spread, a premium in basis points, a backtest return, a change worked out from our own snapshots) is labelled as our calculation with its inputs, and never presented as a provider's number. A valid zero stays zero; a failed read is never an empty list.

Freshness for agents

Every answer from the hosted MCP server carries as_of, the time the provider observed the figure; capture_bucket, the capture window it is filed under, when it has one; and a freshness block with the lane's cadence, its stale threshold, the reading's age and whether it is stale. tools/list carries each tool's cadence and staleness from the table above. See Hosted MCP server and Agents and agent access.

An answer also carries captured_at, when we captured the reading, beside the provider's own time, and staleness is judged by when we captured it (freshness.judged_by: capture_time), so a figure the provider publishes once a day is not called stale an hour after we captured it. A windowed answer carries window: the period asked for against the period stored, and every stretch with no captures. A stretch counts when two captures are further apart than 1.5 times the lane's step plus 15 minutes (on a sampled series, at least 2.5 times the median spacing), and the charts in the app break there instead of drawing a line across it. The short text summary names the key figures, the window and its gaps, so a client that reads only text gets them too.

Republishing our figures

You may republish figures Investor Intel calculates, in a newsletter, a post or a report, paid or free, with the line "Calculated by Investor Intel (thecontentforge.io/intel)". On the pages they are the figures labelled as our calculation; in agent results they are marked calculated_by: investor_intel.

Figures from CoinMarketCap, CoinGecko and other providers are theirs. Republishing them needs permission first: ask us at support@thecontentforge.io, and the provider's own terms apply. A newsletter sent to paying subscribers counts as republishing. CoinMarketCap figures are shown to signed-in members with "Data provided by CoinMarketCap.com".

Your own entries, such as quantities, prices paid, notes, alert levels and theses, are yours.

Every MCP result and agent API read carries a licence field with this rule; see Hosted MCP server.

Terms

The market words the app defines on tap (a dotted word, or the small info mark beside a column heading) come from the Investor Intel glossary, word for word. The app also lists them on its own Methodology page, under Terms.

Last updated