TRADING4AILegacy strategy detail archive

Legacy archive

This noindex page is a legacy archive.

The current public product is Financial Agent Reliability Materials. This route is retained as historical reference only and does not represent the current Pages-only offer, live order flow, strategy sales, or backtesting service.

Legacy strategy detail archive

Market Regime Filter

A compact state machine for deciding whether aggressive strategy calls should even fire.

FreeCallableBTC + ETHMachine Judgement Only

Quick actions

/api/v1/strategies/market-regime-filter/invoke

Best for

A market-state filter that decides whether crypto conditions are risk-on, transitional, or defensive.

Market scopeCrypto
Strategy familyRegime Filter
Delivery typeAPI Response
Verification levelMachine Judgement Only

Use this when

  • Gate downstream breakout systems when BTC and ETH confirm directional strength.
  • Prevent agents from invoking high-beta tactics when the market is structurally weak.
  • Provide a stable regime label for downstream prompts and tools.

Evidence available

  • Built from recent public discussion around BTC reclaiming 76k and ETH reclaiming 2400 as regime pivots.
  • Best suited for top-down filtering, not micro entries.

Inputs and assumptions

These inputs, evidence requirements, and execution assumptions define what the strategy expects before the result is trustworthy.

InputsBTC price / ETH price / timeframe
Execution assumptions4h | not applicable because the public callable does not place orders

Delivery path

Free strategies return an API response. Paid artifacts move through order, claim, entitlement, and evidence-gated delivery.

{
  "btc_price": 76140,
  "eth_price": 2412,
  "timeframe": "4h"
}
{
  "status": "success",
  "data": {
    "regime": "risk_on",
    "confidence": 0.84,
    "reason": "BTC and ETH are both above the current threshold set."
  }
}

Agent-readable surface

Machine surface: /for-agents

Machine bridge: /llms

OpenAPI contract: /openapi.json

Agent card: /.well-known/agent.json

Public trust summary

No public trust summary has been published for this strategy yet.

Public trust summaries stay unpublished until manual review approves a public-safe version.

When published, public trust summaries stay limited to evidence_level, review_status, tested_market_scope, tested_assets, tested_time_window, safe_statements, and limitations.

Raw evaluation history, operator notes, blocked claims, rankings, and performance-winner language stay internal.

Limits and non-promises

Historical strategy reference only: this page is not a current strategy recommendation, checkout path, or live performance claim page. Current public work starts at /agent-verification/materials and the active scope is summarized at /current-capabilities.

  • Tick-by-tick execution decisions.
  • Single-asset forecasting without broader market context.
  • Markets outside crypto without recalibration.

What it does

A market-state filter that decides whether crypto conditions are risk-on, transitional, or defensive.

Best forTop-down crypto regime checks / Agent routing before invoking higher-beta strategies
UniverseBTC / ETH

How it works

  • Compare BTC and ETH against explicit launch thresholds.
  • Classify the environment into risk_on, transition, or risk_off.
  • Return a confidence score and thresholds so downstream agents can explain the route.

Risks

  • Tick execution
  • Single-asset prediction without BTC and ETH context
  • This is a gating signal, not an entry signal.
  • Thresholds must be recalibrated before using it outside the current crypto context.

Evidence

Backtest requiredno
Data requirementsBTC price / ETH price / timeframe
Minimum diagnosticsno_trade / overtrade / drawdown / data_gap

Deliverables

  • strategy_card
  • invoke_schema
  • example_response

LEAN-like components

AlphaRisk appetite improves only when both major crypto anchors clear their current thresholds.
PortfolioNo position sizing; use as an upstream allocation gate.
Riskblock high-beta tactics in risk_off / require multi-asset confirmation
Execution4h | not applicable because the public callable does not place orders | not applicable because the public callable does not place orders