S4 Signal402
Agent OS No credentials in browser

Signal402 / Binance Agent OS

A decision layer for agent trading.

Signal402 turns live Binance context into an evidence backed decision. A second agent can request a briefing, but a real order is only possible after strict risk checks, dashboard approval, and explicit confirmation.

Open local operator console Read the source

This public page is a safe front door. The live console stays with the authenticated agent host.

Control path

Evidence before execution

CONNECTION REQUIRED
  1. 01ContextBinance MCP market and account readsWAITING
  2. 02Risk envelopeDeterministic checks with an evidence hashWAITING
  3. 03Human approvalExact symbol, side, quantity, and capLOCKED
  4. 04ReconciliationReal order event, fill, position, and balanceLOCKED
No simulated receipts, fills, balances, or order IDs.

What the agent does

It sells clarity, not a promise.

  • Publishes a live Spot or Futures briefing through the Seller Agent.
  • Uses Binance MCP data and runtime tool discovery when connected.
  • Runs DeltaZero style risk gates before any executable proposal.
  • Records real B402 settlement and real Binance order evidence only.

Hard boundaries

The control room can say no.

  • No withdrawals, transfers, or credential handling in Signal402.
  • Every order needs dashboard approval and a final CONFIRM.
  • Futures are isolated margin, maximum 3x leverage, maximum 10 USDT notional.
  • Neutral and COIN M Futures paths are report only in v1.

Futures mode

Risk first. Direction second.

USDⓈ M directionalIsolated only≤ 3x≤ 10 USDTNo automatic leverage changes