Optic for Binance — every Binance market at once

01One engine · Binance kits

Markets disagree. That disagreement is the signal.

The exchange prices leverage. The chain prices holders. The prediction market prices the outcome. The crowd prices the story. Single-domain agents read one and call it truth. Optic reads them together and reports the gap — on Binance, through Binance.

01 — READ

Every Binance market at once

Spot + perps through the Binance MCP Server, onchain through Binance Web3, outcomes through Binance Wallet prediction markets, attention through the social-hype board — one query fans out across all of them.

02 — RESEARCH

The homework behind the numbers

Live web research — form, catalysts, macro — so a read is never just a data printout. Sources cited on every brief.

03 — SCORE

Score the gap

A 0–100 gap score, a decisive verdict line, and a shareable card. Observational language, lint-gated in code — never a trade instruction.

04 — ACT

Hand over the ticket

Decided? Optic constructs the exact order — market, outcome, size — as the caller's own Binance rails: a confirm-before-execute MCP order, or the two baw prediction trade commands for the Agentic Wallet. Optic signs nothing.

Two market feeds tracking the same story, then diverging — the gap is the signal — Two venues, one story — until they diverge. That gap is the read.

02Binance kits only

Built on Agent OS, end to end.

Nothing outside the Binance stack touches the data path. Every venue below is a Binance kit, and the exchange leg comes through the same MCP server a human would connect to Claude Code.

Venue	Binance kit	What Optic reads
exchange	Binance MCP Server · Binance API	spot price, 24h, volume · funding, open interest & its 24h change, account skew, taker flow, perp basis
onchain	Binance Web3 token APIs	price, liquidity, holders · dev / sniper / bundler / insider / smart-money / KOL / Binance-user cohorts · activity acceleration
prediction	Binance Wallet prediction markets (BNB Chain)	priced probability, volume, liquidity, end time — ranked by relevance before size
attention	Binance Web3 social-hype board · topic radar	relative hotness, trend, sentiment label, the board's AI summary, KOL count · hot narratives for stories
safety	Binance token security audit	contract-mechanism hits, taxes, concentration → 0–100 risk score
smart money	Binance Web3 smart-money signals · inflow rank	who is accumulating what — wallets, inflow, exit rate
stocks	Binance-listed Ondo tokenized stocks	on-chain per-share price vs the real close vs analyst consensus

03Ten services · one endpoint each

One query, the full picture.

Every service is a POST that returns a JSON verdict plus a card. No login, no dashboard, no API key.

Endpoint	Service	Input	Returns
POST /v1/read	Full Market Check	{"query": ticker · address · story}	exchange + onchain + prediction + attention + safety + smart money → gap score, reasoning, card
POST /v1/read	Market Scan	{"query": "what's heating up"}	social-hype accelerators, hot narratives, fresh launches, smart-money inflow
POST /v1/daily	Today's Picks	none	decisive, research-backed calls across Binance Wallet prediction markets and Binance Web3 momentum
POST /v1/edge	Mispriced Markets	none	where a Binance Wallet prediction market's price looks soft or rich vs research
POST /v1/stocks	Stock Check	{"query": "NVDA"}	Ondo tokenized share vs the real close vs analyst consensus
POST /v1/rug	Token Safety Check	{"query": address · ticker}	Binance security audit + holder composition → 0–100
POST /v1/smart-money	Smart Money Watch	none	tokens Binance-tracked smart money is accumulating
POST /v1/timing	Too Early or Too Late?	{"query": token}	lifecycle stage from age, hype trajectory and activity acceleration
POST /v1/pulse	Up/Down Pulse	none	BTC · ETH · SOL Up/Down windows on Binance Wallet vs the Binance spot tape
POST /v1/ticket	Order Ticket	{"query", "side": yes\|no, "usdt"}	the exact baw prediction trade quote + place-order commands for your Agentic Wallet

04For agents & builders

Your agent can read the gap in one request.

Plain HTTP, JSON in, JSON out. Install the skill and any Agent OS client — Claude Code, Codex, ChatGPT, OpenClaw — can call it by name. Then act on Binance's own rails.

quickstartPOST · JSON

# 1 — a full cross-venue read
curl -s -X POST https://optic-binance-production.up.railway.app/v1/read \
  -H "Content-Type: application/json" -d '{"query":"BTC"}'

# 2 — turn a decision into Agentic Wallet commands (Optic never signs)
curl -s -X POST …/v1/ticket -H "Content-Type: application/json" \
  -d '{"query":"Fed decision in September no change","side":"yes","usdt":25}'

# 3 — or run it as an MCP server, beside Binance's own
claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic
claude mcp add optic --transport http https://optic-binance-production.up.railway.app/mcp

Binance's MCP Server only accepts its own approved agent clients, so Optic never asks to hold your session — it joins the one you already have. Your agent pulls the exchange leg with its Binance tools and passes it into optic_read; Optic reports that leg as binance-mcp because that is where it came from. Every order Optic constructs is still confirmed by you, in your own sub-account or Agentic Wallet.

Every Binance market, read at once. The gap between them is the signal.