Methodology

Market Status Methodology

This page defines the public Market Status metrics used across ConfluenceMeter — designed to be citable. It explains what the numbers mean, what they do not mean, and how to interpret them without overfitting.

Use as context, not signalsHub updated ~5 minutes1h closes stored as historyMarket data is probabilistic
Press / Data
Quick links for referencing ConfluenceMeter

If you want to reference Market Status in an article or newsletter, use the hub link + the “As of” timestamp shown on the page. For reproducible references, link the CSV export you used.

Hub
https://confluencemeter.com/market-status
Rankings + distribution + “As of”.
CSV snapshot
https://confluencemeter.com/api/public-dashboard?format=csv
Latest hub snapshot for citations.
CSV example (BTC 1h history)
https://confluencemeter.com/api/market-status/pair?pair=btc-usdt&format=csv&series=history_1h
Closed 1h history series export.
Definition
Score (0–100)

The Score is a compact summary of confluence for a timeframe.

  • • Around 50 often means mixed conditions.
  • • Farther from 50 means clearer directional bias in that timeframe.
  • • A low score is not “bad”; it can be clear bearish bias.
Neutral zone: ~40–60Clearer: <40 or >60
Definition
Clarity (confidence, 0–100)

Clarity is the confidence in the score (scaled to 0–100). Higher clarity generally means fewer conflicts/noise for that timeframe.

  • • High score + low clarity = “looks strong” but is noisy.
  • • Low score + high clarity = “clean bearish conditions.”
  • • Clarity is a filter against overtrading.
75–100: very clear50–74: decent0–49: noisy
Definition
Regime label (trend/range/chop)

The Regime label is an explainability tag for market conditions.

  • trend: directional conditions are more plausible.
  • range: mean-reversion / back-and-forth is common.
  • chop: high noise, whipsaw risk.
Regime is not a guarantee — it’s a label to reduce misreads and overconfidence.
Definition
Agreement (1h-led)

Agreement measures how consistent timeframes are with the 1h stance (bull/bear/neutral).

  • • High agreement = fewer timeframe conflicts.
  • • Low agreement = mixed stack → higher noise risk.
  • • Neutral stance is valid: it means 1h conditions are not clearly biased.
70%+ = highly consistent40–69% = mixed stack<40% = conflict-heavy
Data
Update cadence and history
  • Hub refresh: roughly every ~5 minutes.
  • History series: uses closed 1h candles (more stable than live ticks).
  • Data availability: new symbols may show limited history until enough 1h closes have accumulated.
Practical tip: use Clarity + Agreement first. The score alone is not enough.
What it is NOT
Not a signal service

Market Status is not “buy/sell.” It is a conditions filter.

  • • A high score does not mean “buy.”
  • • A low score does not mean “sell.”
  • • You still need your execution plan and risk rules.
Treating context metrics as signals is how you overtrade.
Limits
Limitations and edge cases
  • • Sudden news events can invalidate recent context.
  • • Low-liquidity assets can have noisier readings.
  • • During extreme volatility, clarity may drop even when score swings.
  • • If history is limited, treat long-horizon claims cautiously.
Always interpret the data with timestamps and context.
Citable source
How to cite

Use the hub or a symbol page as your referenced page, plus an access date/time. For reproducible references, link the CSV export used.

Suggested citation
ConfluenceMeter — Market Status Methodology. Accessed 2026-03-06. https://confluencemeter.com/market-status/methodology
Exports (recommended)
  • • Hub snapshot CSV: https://confluencemeter.com/api/public-dashboard?format=csv
  • • Symbol 1h history CSV (example): https://confluencemeter.com/api/market-status/pair?pair=btc-usdt&format=csv&series=history_1h