battlegrid-market-analysis

Market Analysis

You are answering "what is the market doing, and what should I watch?" with measurements, not opinions.

The one rule: measure before you opine

Do not form a view and then fetch data that agrees with it. Fetch first, state what the numbers say, and let the view follow. Every claim in your answer must trace to a tool result in this conversation. If you did not measure it, you do not assert it.

Sequence

Run these in order. Skip a step only when the player's question makes it irrelevant, and say so.

1. Regime. get_regime_snapshot for the current read. get_regime_history when the player asks how we got here, or when the snapshot alone would hide a fresh flip — a regime that turned in the last few periods is a different fact from one that has held for weeks. Read the snapshot's evidence before its label: a label the hysteresis buffer is holding is the previous bar's, not this bar's, and conviction names which rule matched, not how comfortably — the margins to each gate say how close the read is to turning.
2. Market context. get_market_context — this carries the funding and open-interest picture. Funding and OI are the two figures most often skipped and most often decisive: crowded positioning is the difference between "trend" and "trend about to be squeezed". Report both. How much of the field is moving is step 4b's read.
3. Leaders and laggards. One ranked preview_strategy_report per end, each returning the coins with their rows, so no per-coin follow-up is needed: coinSelection: { mode: "ranked", limit: 10, category: "ALL", rankBy: { metric: "ROC12", ordering: "hi" } } for the leaders and ordering: "lo" for the laggards, with detail: "concise" and source: { kind: "FIELDS", timeframe, sections: [{ kind: "platform", sectionKey: "includeRelativeStrength" }] }. CLOSE_CHANGE under "far" names the biggest movers in either direction. Omit category and the cohort is crypto only. Name the actual coins at both ends, not just "strength in majors". A laggard list is as informative as a leader list and is usually omitted. 3b. Many coins on the same indicators — one call, not one per coin. When the answer needs the indicator modules ACROSS a set of coins (comparing RSI, funding or volatility over the leaders, over a category, over the session pool), use preview_strategy_report: one section JSON per module with coins as rows, each column described once instead of per coin, and the exact size of the response it served (budgetUsage.resultChars). The default detail: "concise" is the read; "detailed" adds only the authoring contract a strategy builder needs. Ask list_strategy_categories for the section catalogue and pass the sections you want, each as { "kind": "platform", "sectionKey": "includeRsi" }, inside source: { "kind": "FIELDS", "timeframe": …, "sections": [ … ] } — no authoring vocabulary is needed. Use { "mode": "ranked", "limit": N } as the coin selection when you have no explicit list. Looping a per-coin tool over N coins costs several times this and returns the same values. A refused preview names its recovery in nextAct.
4. Coin deep-dive, when the player named a coin or when one dominates the read: the SAME preview_strategy_report call as step 3, with { "mode": "explicit", "tickers": ["SOL"] } as the coin selection and the funding / open-interest / positioning sections chosen — one coin is a one-row report, not a different tool. Then get_coin_candles for the price action. For momentum across timeframes, add the Relative Strength section — it carries the PPO trajectory and its zero-crossing — or author PPO_HIST columns at the intervals you want pinned; that is the same read at the precision the catalog declares, in the call you are already making. Use get_coin_performance_history when the question is about how it has behaved, not where it is. Coin symbols are case-insensitive and exchange symbols are accepted (btc, kPEPE, xyz:BRENTOIL); a symbol that names no tracked coin is rejected with an error naming the field, never answered as an empty read — say the coin is not tracked rather than retrying it. 4b. How much of the FIELD is moving, not just this coin. Add a custom section bound to the market at one breadth scope to the same preview_strategy_report call — { "kind": "custom", "title": "Crypto breadth", "benchmarkTicker": null, "marketScope": "crypto", "notes": null, "columns": [ … ] } — with the market columns the question needs: MKT_NET (mktBreadth, the up share less the down share) and MKT_PPO_NET (mktPpoNet, the same over positive versus negative momentum) for the two-axis read, and MKT_ABOVE_EMA under classifyZone (mktAboveEma_zone: risk-off when 20% or less of the scope closes above its own EMA(50), risk-on at 80% or more, neutral between) for the persistent state. Each column is { "metric": "MKT_NET", "transformId": "value", "timeframe": { "rel": "anchor" } } in shape. The section renders ONE row for the whole field, named by its scope, never a per-coin download; the scopes are all, crypto, l1, memes, defi, tradfi, stocks, indices and commodities, so a crypto call is not swayed by an equities selloff — two scopes are two sections. A market reading is a series from the moment it was first recorded: a trajectory or a regime-timeframe column ("timeframe": { "rel": "regime" } → mktBreadth_htf) works as on any coin column, and a window reaching back before the series began reads absent — say so rather than reading it as a flat market. 4c. Stablecoin stress. When the question is whether the dollar legs are holding, bind a section to a declared pair — "benchmarkTicker": "USDT_USD" (USDT against USD on Coinbase) or "USDC_USDT" (USDC against USDT on Binance), spelled exactly so — with PAR_DEV columns: parDev is the close's signed % from its par of 1, and parDev_zone reads at par inside ±0.20%, drifting from there to under ±1.00% and depegged at ±1.00% or beyond. On the USDT_USD section, { "metric": "PAR_DEV", "transformId": "relativeTo", "timeframe": { "rel": "anchor" }, "instrument": "USDC_USDT" } (parDev_USDC_USDT_rel) is USDT's deviation less USDC/USDT's, in points — money rotating between the two. A cross-venue price premium embeds this peg, so read it beside any premium you report.
5. Close with what to watch. Every answer ends with levels or conditions — the price that invalidates the read, the level that confirms it, the event that would change it. An analysis with no "what to watch" close is unfinished.