BRS Signals

Current Bitcoin block height from mempool.space.

How much do the three independent sensors agree right now?

Call this BEFORE trusting any directional read. Agreement is scored pairwise: 1.00 same meta-regime, 0.85 same direction, 0.60 one sensor silent, 0.25 open conflict, 0.00 unreadable. High agreement means conditions are worth acting on; low agreement means the sensors are looking at different markets and the honest answer is wait.

Returns all three verdicts (X-Ray on-chain, Pulse off-chain, Shadow absence), the convergence score, the dominant meta-regime (TRENDING_UP, TRENDING_DOWN, RANGE_ACCUMULATION, RANGE_DISTRIBUTION), shift_brewing (entropy rising = regime change may be imminent), gamma exposure, and the system entropy gradient.

The full picture in one call (Pro). Use the individual tools when you want one answer cheaply; use this when you want everything at once.

Bundle: regime + signal + funding + suppressed signals.

Returns: - regime_meta: Full regime classification with confidence and range info - signal: Latest bullish/bearish/WAIT with confidence and reasoning - funding: Cross-exchange funding squeeze data - suppressed: Signals that were filtered by the noise detector - cycle_context: Time cycle analysis (if available) - options_context: Deribit options market context (if available)

This is the most comprehensive single endpoint — use it when you want the full picture in one call.

Should you be trading Bitcoin right now, and in which direction?

Returns side (bullish / bearish / WAIT) with confidence, the regime and zone the call was made in, the reason, btc_price and timestamp. WAIT is the most common answer and means no edge exists — respect it; do not force a trade. Confidence is normalised against how much evidence was reachable: sent signals typically land 0.30–0.50, so compare against the distribution, not 1.0. Signals suppressed by the noise filter are shown (suppressed=true), never hidden.

Requires a Pro API key or x402 payment. Free alternative: get_convergence.

Who is transacting on-chain right now — X-Ray's raw read (Pro).

The mempool fee curve shape: FLAT_WIDE means patient accumulation, STEEP_TALL means urgency or panic, BIMODAL means whale activity.

Returns: - curve_type: FLAT_WIDE (accumulation), STEEP_TALL (retail panic), BIMODAL (whale activity), etc. - actor_profile: Inferred actor behavior from fee distribution - skewness, kurtosis: Statistical shape of fee distribution - gini_coefficient: Inequality of fee spending (low = uniform, high = whales dominating) - entropy: Diversity of fee usage (high = diverse activity, low = single-actor dominance) - tx_count: Number of transactions analyzed

FLAT_WIDE fee curves indicate accumulation (whales being patient). STEEP_TALL fee curves indicate urgency/panic (retail rushing transactions).

Is positioning one-sided enough to squeeze? (Pro stream)

Cross-exchange funding spread, velocity, and squeeze probability. Contrarian by design: the market usually reverses against the crowded side.

Returns: - squeeze_probability: 0–100% chance of a funding squeeze - divergence_direction: Which direction the divergence points (BULLISH/BEARISH/NONE) - max_spread: Maximum spread between exchange funding rates - spread_velocity: How fast the spread is growing (%/min) - Per-exchange rates: Binance, Bybit, OKX, Hyperliquid

High squeeze probability means traders are piling onto one side — the market usually reverses against them. This is a contrarian signal.

Where does dealer hedging amplify or dampen the move? (Pro stream)

Net dealer gamma and the flip level that acts as a price magnet.

Returns: - dealer_net_gamma: Net dealer gamma position - gamma_flip_level: Price level where gamma flips (key support/resistance) - put_gamma, call_gamma: Put and call gamma separately - gamma_regime: Current gamma regime interpretation

Gamma flip levels act as magnetic price levels. Above flip = dealers hedge with the trend (accelerating). Below flip = dealers hedge against the trend (dampening). Large negative gamma = explosive potential.

Live Bitcoin mempool fee rates from mempool.space.

Returns recommended fees in sat/vB: fastest, half-hour, economy, minimum. Fees above 50 = congestion, above 100 = extreme. Critical for X-Ray sensor verification.

Live mempool stats: pending tx count, total size in vbytes, total fees in BTC.

High pending count (>200K) = congestion. Low count (<50K) = quiet.

Which game is the market playing right now?

Returns the current regime with conviction and how long it has held — accumulation, distribution, trending, reorganizing — as latest_event plus all active_events. Use it to pick the playbook (trend-following vs mean-reversion vs sit out) BEFORE interpreting any individual reading. Free tier, no key needed.

The public audit trail: recent calls and what Bitcoin did next.

Each record carries timestamp, side, confidence, regime, zone, reason, plus outcomes where resolved (+4h/+24h returns, worst drawdown). Use this to verify rather than trust: the entire record is public, and auditing it is the intended use. Nothing is withheld and outcomes are never re-scored after the fact.

Args: limit: Number of recent signals to return (1–200, default 20)

Whale buying or selling intent before it reaches exchanges (Pro).

Large USDT (Tron) and USDC (Solana) movements: inflow surges precede buying pressure, outflow surges precede distribution.

Returns: - flow_regime: NORMAL, INFLOW_SURGE (buying pressure), OUTFLOW_SURGE (selling pressure) - total_net: Net stablecoin flow (positive = accumulating, negative = distributing) - Recent significant transfers over $1M

Whale stablecoin flows detect buying/selling intent BEFORE it reaches exchanges. Large USDT inflows to exchange wallets = imminent buying pressure. Large USDT outflows from exchange wallets = whales cashing out.

The sample size behind everything: signals sent, data points collected, days collecting. Small samples cannot prove an edge — this tells you exactly how small.

Returns: - signals_fired: Total number of trade signals generated - data_points: Total on-chain data points collected - days_collecting: How many days the system has been running

Is the instrument operational right now?

Component-by-component status for all collectors and engines. Call this first if any reading looks stale or absent — a sensor being down changes what every other answer means.

Run a read-only SQL query against the BRS SQLite database.

Tables: decoder_decision_records, engine_verdict_records, regime_event_records, vao_records, funding_records, etc.

Use this to check signal history, regime state, or system health without spawning sqlite3 CLI commands.

Args: query: SQL SELECT statement to execute

Returns: JSON array of result rows