Crypto Regime Analyzer describes what the crypto market currently looks like before any coin-level work begins. A Python script combines six weighted components (BTC trend structure, altcoin breadth, BTC dominance, perpetual funding, drawdown and volatility, and momentum) into a composite score, where 100 is the healthiest risk-on reading, and assigns a zone of RISK_ON, NEUTRAL or RISK_OFF.
It needs no API key. It does not pick coins, give buy or sell signals or set price targets. The zones are descriptive heuristics that have not been validated as allocation rules.
What You Get
- A 0 to 100 composite score and a zone (RISK_ON, NEUTRAL or RISK_OFF)
- A per-component table with weight, score and a signal string
- Flags for components that had no data, with the effect on confidence
- crypto_regime.json for chaining into other skills and crypto_regime.md as a one-page report
Common Use Cases
- A daily check of whether crypto conditions look risk-on or risk-off
- Asking whether altcoins are participating broadly or only a few are leading
- Checking whether perpetual funding rates look crowded
- Feeding a descriptive crypto input into an exposure summary
What Makes It Unique
It works with free, keyless public data and has an offline mode, so the same score can be reproduced from a snapshot. Missing components are handled by redistributing weights and reporting the gap. A validation reference states the evidence boundary, so the bands are not presented as tested allocation rules. Dominance history builds up locally one observation per day, and the component reports as unavailable until enough days exist.
Under The Hood
In live mode the agent runs a Python script that calls the public CoinGecko API and the Binance futures endpoint over the network, with throttling for the free tier; the first run of a day can take a few minutes. It caches fetched data and a daily dominance record in a local cache folder (.crypto_regime_cache by default), and writes the JSON and Markdown reports into the chosen output folder, so it creates files and folders on disk. Offline mode makes no network calls. No API key is used. The agent also creates the output folder with a shell command.