BINANCE AGENT OS × CIRCUIT

Real evidence.
Deterministic veto.

This is a recorded proof from 7 September 2026: a Codex-hosted supervisor read fresh BNB/USDT market data from the real Binance Agent OS MCP, supplied that evidence into CIRCUIT, and evaluated two hypothetical Spot BUY intents without executing a Binance write.

VERIFIED LIVE PROOFREAD-ONLY AGENT OS SESSIONBNB / USDT

01BINANCE AGENT OSspot.ticker24hr + spot.depth

→

02CIRCUIT SUPERVISORtyped ActionIntent

→

03DETERMINISTIC POLICYmandate + freshness + runtime

→

04VERDICTBLOCK / ALLOW

INTENT A

BUY $100 BNB

BLOCK

Binance price745.63 USDTCIRCUIT evidence745.63 USDTEvidence age0.684 sBinance writes0

ORDER_CAP_EXCEEDEDDAILY_BUDGET_EXCEEDED

The active mandate allowed at most $10 per action and $30 per day, so CIRCUIT contained the $100 proposal before any Binance mutation.

5fba99e4-8280-45d2-bdaa-61da16f219a3

INTENT B

BUY $8 BNB

ALLOW

Binance price745.50 USDTCIRCUIT evidence745.50 USDTEvidence age0.645 sBinance writes0

ALL_CHECKS_PASSED

The compliant $8 proposal received ALLOW, then stopped at the supervisor’s human-approval boundary. It was not executed.

777aeb09-5106-447b-8329-c25a1cfa298c

WHAT THIS PROVES

Live Binance evidence entered CIRCUIT’s own decision trace.

✓Agent OS connectedReal Binance MCP session✓Evidence matchedBinance price = CIRCUIT evidence✓Freshness passedBoth snapshots under one second old✓Zero Binance mutation callsNo trade, transfer, Convert, Margin, Futures, or cancellation tool invoked

EVIDENCE BOUNDARY

What was live—and what was not.

Live Binance evidence: BNB/USDT ticker price, ticker timestamp, five-level order book, best bid/ask, and calculated spread. Simulation/default evidence: account daily spend, concentration, drawdown, volatility baseline, and prior-settlement state. Those values were not live Binance account data.

This page is a recorded verification snapshot, not a live ticker and not a claim of trading performance. The public CIRCUIT deployment remains simulation-first and exposes no MCP execution tool.

JUDGE PATH

Reproduce the deterministic controls next.

Run Judge Mode to execute all eight adversarial scenarios, then inspect Mission Control and the MCP supervisor.