CoinMarketCap

Static profile for one or more cryptocurrencies, by numeric CoinMarketCap id: logo, long-form markdown description, official website, social / explorer / whitepaper links, category, tags, date added, and, for tokens, the platform and its contract address. No price, market cap or volume. Links only, not the text of the pages behind them - that text is in search_crypto_info, not here. One result row comes back as an array of objects, two or more as {headers, rows}, and the header set varies from call to call, so column positions are not stable. Unknown ids are dropped and duplicate ids collapse, both with no error, so the row count can be lower than the id count; every row carries its own id. No field selection: each call returns the full profile, and the description alone can exceed 20,000 characters per coin.

Recent news and web items for ONE cryptocurrency. Requires an id - there is no market-wide or all-coin feed. One item returns an array of objects; two or more return {headers, rows}, and the columns vary: description is dropped when it is empty for every row. Columns are title, description (a prefix cut of content, sometimes mid-word), content, url, publishedAt, quality (numeric string, scale undocumented). content is an excerpt capped near 2000 chars, not the full article; url is the source. publishedAt is a display string like "3 August 2026 12:53 PM UTC+0", not ISO 8601. Items sort by publishedAt descending, and event or prediction pages carry future dates, so the top item can be a future entry rather than today's news. Asset matching is loose and items carry no id or symbol field, so an item can be about a different asset or not recent, with the title as the only relevance signal. No paging, offset, date, language or source filter; limit can only shrink the list.

Technical analysis of the TOTAL crypto market capitalization - the whole market, not any single coin. Single-coin technical analysis is a different tool, get_crypto_technical_analysis. Takes no parameters. An id, or any other argument, is silently ignored and the response is identical, so a normal response is never proof the data was scoped to a coin. Returns macd; rsi with fixed 7/14/21 windows and no timeframe option; fibonacciLevels (swingHigh, swingLow, retracementLevels, extensionLevels - none of them labeled support or resistance); pivotPoint, on a market-cap basis, not a price; and currentMarketCap plus currentVolume, the whole-market totals. No moving averages. Every value is a display string, not a number: market-cap, volume, MACD and fibonacci figures carry a T/B/M magnitude suffix ("2.15 T"), rsi values do not ("40.15").

Holder and address-distribution analytics for one cryptocurrency: addresses bucketed by the USD value they hold, the whales-vs-others share of circulating supply (percent of supply), addresses bucketed by holding duration, top-holder concentration, and total holder counts. No price, market cap, trading volume or supply totals here. Which blocks come back is decided per coin and does not track market-cap rank, so a major asset can return nothing while a small one returns full top-holder concentration. When a coin has no data the call still returns isError:false and a non-empty body, because every response carries the same static definitions glossary of whale / holder / trader vocabulary - identical across coins, with no per-coin values.

Current market quote for one or more cryptocurrencies - the default tool for price questions. USD only, current snapshot only: no history, no top-N or biggest-mover list. Returns 36 snake_case fields per coin, including price, market_cap, market_cap_dominance, volume_24h, volume_change_24h, fully_diluted_market_cap, circulating_supply, total_supply, max_supply, turnover, rank, date_added and last_updated_time. percent_change_ covers 1h, 24h, 7d, 30d, 60d, 90d, ytd, 1y and all; market_cap_percent_change_ covers the same periods except 60d and ytd. 0 or 1 matches return an array of objects; 2 or more return {headers, rows}. Header order varies between calls, so a column index learned from one call will not hold in the next. Rows come back in the order the ids were given, and id comes back as a string. Each row is roughly 650 characters. isError stays false when nothing is found: an unknown id is dropped silently, so a 5-id call can return 4 rows or an empty array, and inactive coins come back with null price and rank. Missing or null is no data, not a price of zero.

Price technical analysis for ONE cryptocurrency. Returns five blocks, whose keys are also the includeFields values: moving_averages (SMA and EMA, fixed 7/30/200-day), macd, rsi (fixed 7/14/21), fibonacciLevels (retracement and extension), pivotPoint. Windows are fixed - no interval, period or lookback parameter. Every value is a display string, not a number ("63,612.69"). The response echoes no id, name or symbol. Whole-market technical analysis is a different tool, get_crypto_marketcap_technical_analysis.

Global crypto derivatives snapshot, no arguments: open interest and volume for total, futures and perpetuals, each with 24h, 7d, 14d and 30d change windows; one blended funding rate with the same windows; and BTC liquidations by 1h, 4h, 12h and 24h window split long versus short. Values are live intraday and the payload carries no timestamp of any kind, so figures cannot be given an as-of time. Every value is a display string, not a number ("385.08 B", "993,927.14"). Boundaries: funding is one global blended rate, unit not marked in the value and averaging method undisclosed - no per-exchange or per-contract funding. Liquidations are BTC only. No long/short open-interest ratio and no positioning data, so leverage imbalance is not a field here; no options, basis or implied volatility; no history beyond the fixed change windows. There is no symbol, exchange or interval parameter; the same fixed snapshot comes back regardless.

Whole-crypto-market snapshot, USD only, no parameters. Returns one fixed ~5.5 KB dashboard with 8 sections: last_updated, market_size (total market cap), liquidity (24h volume - total, spot, derivatives, plus a spot_vs_perp_ratio), sentiment (fear and greed), rotation (altcoin season), dominance (btc, eth, others), leverage (open interest, average funding rate, and BTC-only liquidation totals with no long/short split), and trad_fi_flows (BTC and ETH spot-ETF AUM). Windows come from a fixed vocabulary - 24h/7d/30d change, yesterday/last_week/ last_month history, yearly max/min - and not every section carries all of them. ETF data is AUM levels only; net inflow or outflow is absent, and AUM differences are not flows. Every value is a display string, not a number - T/B/M suffixes and +/- glyphs ("2.15 T", "389.54 B", "+58.4%"), timestamps as rendered text ("3 August 2026 12:00 AM UTC+0"). Dominance carries a leading + but is a share of total market cap, not a change. The fear-and-greed and altcoin-season index integers are the only numeric fields, and the altcoin-season regime is delivered as that index on a 0-100 scale. About 1.4 KB of the payload is definition prose. Freshness is mixed: open interest, market-cap changes, volume and dominance move intraday, while fear and greed, altcoin season and ETF AUM come from a daily 00:00 UTC snapshot. last_updated is that daily label, not the as-of time of the intraday fields. There is no asset, convert-currency or window parameter: the reply is always this same whole-market USD payload.

Forward-dated crypto catalysts extracted from news articles - a news-derived catalyst list, not an authoritative economic calendar. Because dates are read out of article text, a dated claim inside an article, such as an analyst target or a prediction-market quote, can surface as a row with the same shape as a scheduled event; the row does not distinguish the two. Which event types are present at any time follows the upstream news corpus, so a type absent from the response reflects the corpus, not the absence of a scheduled event. Returns one key upcomingEventNews as headers plus positional rows: title, content, url, eventDate, originalNewsContent. Row order is unsorted and changes between calls, so the first row is not the nearest event, and one event can occupy several rows sourced from different sites. content is a snippet hard-cut at 100 characters, often mid-word. The full text, and the country or jurisdiction an event belongs to, appear only in originalNewsContent. eventDate is a display string - for example "10 August 2026", sometimes with a time and UTC offset - not ISO-8601. One call returns tens of KB, most of it source-article text, and cannot be narrowed: no parameters, no date, type or region filter, no way to change the row count.

Semantic search over ONE cryptocurrency's own published pages - its website, whitepaper and community forum. Returns 2-3 rows of url, title and raw page text: an uncleaned scrape carrying navigation noise, one row can exceed 85,000 characters, and a row's content can be empty. id is a hard corpus filter: it alone decides whose pages are searched, and the prompt cannot reach outside it. "What is bitcoin?" under Ethereum's id returns Ethereum's whitepaper with no error; each row's url shows which site it came from. No relevance floor - an unrelated prompt or a keyword-only match still returns top-ranked rows and no error. prompt and id are the only inputs: nothing selects result count, text length, document type or language. Structured fields - logo, links, tags, contract address - are in get_crypto_info, not here.