Documentation

APEX is the research and risk layer for your agent.

APEX scans Binance-listed markets, finds conditions worth investigating, makes Bull and Bear argue from the same evidence, applies a deterministic Constitution Referee, and finishes with a Guardian safety check.

1. Open Markets and inspect a route.
2. Open Agent review, enter the book and proposal you want checked.
3. Watch the live council: Bull → Bear → Referee → Guardian.
4. In your own agent, call APEX first, then use Binance MCP to re-check the account and ask for your confirmation before any write.

Open Binance's official Agentic MCP guide ↗

What you should see during a review.

On the dashboard, the Agent council panel is always visible. It starts as Ready, changes to Debating while a review is running, then shows each live result. A public APEX review can end with Referee APPROVE + Guardian BLOCK: the proposal passed portfolio rules but APEX is not authorized to submit a Binance order.

All Binance-listed markets are indexed; routes are scored from live-readable data.

The dashboard loads Binance trading metadata for Spot and USDⓈ-M Futures, including base assets across major tokens, memes and other listed instruments. It reports the full indexed universe and separately scores the most liquid USDT routes so the page remains responsive and Binance rate limits are respected.

Binance may list tokenized or stock-linked products depending on product availability, account and jurisdiction; APEX does not label them as conventional equities. They appear in the universe only when Binance reports them as tradable, and a route is never invented when evidence is absent.

Scores are rankings, not probability of profit. Funding carry is an estimate, not guaranteed yield. News is matched public headline evidence, not social consensus.

Connect APEX and Binance to the same agent.

Install or configure both servers in the AI client you use. Do not open an MCP endpoint in a browser and do not paste an endpoint into a chat asking the model to install it. Use the client's MCP/server settings or documented CLI.

APEX MCP · analysis

{"mcpServers":{"apex":{"url":"http://38.49.209.149:4174/mcp"}}}

This is the temporary HTTP endpoint. Some clients require HTTPS; replace the host with your HTTPS domain when available and keep /mcp.

Binance MCP · account and trading

Follow Binance's official client setup guide ↗. Binance documents market data, Agentic account reads, Spot, Margin, Convert, USDⓈ-M and COIN-M Futures. Withdrawals are unavailable and non-read actions require your confirmation.

Authorization sequence

1. Add Binance in the client.
2. Authenticate through Binance's authorization page.
3. Grant only the scopes needed. Use the dedicated Agentic sub-account and fund it manually through Binance.
4. Add APEX in the same client.
5. Call apex_status, then ask Binance MCP for a read-only BTCUSDT price and balance. Confirm which server handled each call.

Mac, Linux and Windows setup.

Use Terminal on macOS/Linux or PowerShell on Windows. Binance's official guide is authoritative for the client-specific flow.

Codex CLI

# APEX
codex mcp add apex --url http://38.49.209.149:4174/mcp
# Add Binance from the official guide, then authenticate
https://developers.binance.com/en/docs/agent-native/mcp-server/agentic

Run codex mcp list and authenticate the Binance entry. Use the future HTTPS APEX domain for clients that reject HTTP.

Claude Code

claude mcp add --transport http apex http://38.49.209.149:4174/mcp
claude mcp add --transport http binance-mcp-server https://agent.binance.com/mcp/agentic
# open /mcp, select Binance, authenticate

Claude Desktop

Settings → Developer → Edit Config. Add both entries to mcpServers:

{
  "mcpServers": {
    "apex": {"url": "http://38.49.209.149:4174/mcp"},
    "binance-mcp-server": {"url": "https://agent.binance.com/mcp/agentic"}
  }
}

Restart Claude Desktop and complete Binance browser authorization.

Cursor, VS Code and Antigravity

Open MCP / MCP Servers / Tools settings, choose remote HTTP or Streamable HTTP, create apex and binance-mcp-server, and paste the two URLs. If JSON is required, use the same mcpServers shape. Antigravity builds may call this area Tools, Connectors or MCP Servers.

ChatGPT web and Claude chat

When your plan and workspace expose custom remote MCP connectors, open Settings → Apps / Connectors / MCP, add APEX as a remote MCP server, then add Binance through Binance's official connector flow. Do not paste endpoints into a normal chat message. If custom remote MCP is not available in the chat product, use Claude Desktop, Claude Code, Codex CLI, ChatGPT/Codex Desktop or another client with remote MCP support.

Operating-system notes

PowerShell, Terminal and shells use the same URLs. Reopen the shell after installing a CLI. Never put a Binance API key in APEX or the public VPS; Binance MCP uses its own authorization flow.

Four analysis tools.

{
  "book": {"walletBalance": 1000, "positions": []},
  "sessionOpeningEquity": 1000,
  "proposal": {"symbol": "BTCUSDT", "side": "LONG", "qty": 0.001},
  "thesis": {"invalidation": 70000}
}

These are syntax examples, not trade advice. Ask your agent to show the evidence, both arguments, Referee checks and Guardian checks.

What is and is not live.

• Market data, funding, candles, order books, trades and matched public news are live reads when available.
• The indexed universe is broader than the detailed route scan. Failed or unsupported products are shown as unavailable, never silently scored.
• Full portfolio risk review currently covers BTC and ETH USDⓈ-M cross-margin estimates. Spot, isolated margin, inverse, options, Earn and stock-linked product risk need separate models.
• The public APEX dashboard and MCP have no Binance write endpoints. Binance execution remains in the user's authorized agent client.
• APEX's Guardian block is expected when execution authority is absent. Do not describe an APEX approval as Binance authorization.
• News sentiment is source-backed headline classification. Missing coverage is not neutral sentiment.

Common setup problems.

Binance official documentation ↗