Skip to main content
Four commands under shumi market and shumi regime answer “what is the whole market doing”: breadth counts, a flip check, market totals and the regime signal log. For a one-word answer, run shumi market health --context and read summary and regimeAge.dominant: which side is winning and for how many days. The plain call gives the counts behind it.
Add --context for the fuller bundle described below.
The plain call returns the coin count in each trend state, refreshed every 5 minutes:
UP and DOWN are coins in a daily uptrend or downtrend. HODL means the coin’s trend disagrees across quote currencies (up in dollars, down against BTC, for example), so it counts as sideways. hasExtremes and extremes list extreme movers when there are any. --context adds the dollar-only view, which counts UP and DOWN only, plus the fields below. Read summary first, then regimeAge and stressIndicator.

Check whether the market has flipped

API: GET /api/cli/market/crossing. Agent tool: get_market_crossing. A crossing is one trend group overtaking another across the market, for example DOWN coins outnumbering UP coins. When none has fired you get an empty crossings list and "message": "No crossing detected".

Get BTC dominance and market totals

API: GET /api/cli/market/global. Agent tool: get_global_market.

Read the regime signal log

Bare shumi regime prints help only.
The regime model tracks long trades. The log shows it entering when price touches the lower band of its range and leaving at the upper band, on a time stop or on a stop loss. long_entry means the model opened a long. long_exit means it closed at the upper band, in profit or not. time_stop_long means it ran out of time. exit_long_stop means it hit its stop. regime signals lists those entries and exits, newest first, 20 per call. data.meta.total holds the full count (106 at the time of writing). regime history BTC returns that coin’s tracked outcomes, in trades, and currentPosition, which is empty when no entry is open. Each outcome has: For “is the market up or down right now”, use market health --context and market crossing above.