What the corpus is actually talking about right now, ranked, each with a sentiment score and a link into the tag taxonomy.
A rolling window, not a corpus — 18 is the complete current set, and it turns over as coverage moves. The value is the ranking, not the volume.
Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.
A curl that runs against the live API right now, plus the MCP tool names for the same data.
MCP tools
get_trending_keywordsget_trending_keywords_detailThree concrete questions this capability answers that a general crypto API does not.
/cookbook/crypto-research-agent runs.keyword.tag.slug, and that slug is accepted by every other feed — so a trending term turns straight into news, governance and price queries.trendiness says how much attention a term is getting, sentiment_score says how the coverage reads. A term trending hard at negative sentiment is a different story from one trending hard at positive.Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.
There is no history.
The endpoint returns the current window only. There is no date parameter and no archive, so "what was trending last Tuesday" cannot be answered — snapshot it yourself if you need a series.
The set is small and complete.
total is 18 and all 18 come back in one page. Pagination is unnecessary, and a limit above 18 changes nothing. Do not build an infinite scroll on it.
Scores are strings.
sentiment_score and trendiness are quoted decimals — "0.63", not 0.63. Sorting without casting gives lexicographic order.