Nexus

Start here

• Nexus — modules, webhooks, channels, trading prep
• Nexus bot — inbound webhook, wallet follows, execution settings
• Product overview — features and trust boundary
• Support — in-portal threads

Inbound webhook

Copy your URL from Nexus bot → Modules. Keep the UUID private — anyone with it can submit alerts for your account. Enable the webhooks and trading_bot modules before testing. This URL is for your bot only. Publishing to followers uses a published webhook strategy. Desk Ticker overlays use Portal inbound alerts — same signals page.

JSON (recommended)

POST https://nexus.mrtrades.com/webhook/<uuid>
Content-Type: application/json

{
  "action": "LONG",
  "symbol": "BTCUSDT",
  "sl": 64000,
  "tp": 67000,
  "leverage": 3,
  "reason": "tv_alert"
}

• action — LONG, SHORT, or CLOSE
• symbol — e.g. BTCUSDT (perp suffixes like .P are stripped)
• sl / tp — optional stop / take-profit prices
• leverage — optional; falls back to bot auto-trade settings; capped at 5× on webhook entries
• reason — optional journal tag

Execution path

1. Request is audited, then forwarded to the bot webhook handler.
2. Modules must be enabled: webhooks + trading_bot.
3. LONG/SHORT call the same entry path as the bot (margin/leverage from auto-trade config when omitted).
4. CLOSE exits the open position for that symbol (or all if omitted, depending on payload).
5. Live trading stays off until you set up live trading and turn it on.

Usage & APIs

• Bot UI shows hits 24h / 7d and last action — backed by GET /v1/nexus/inbound-webhook/usage
• OpenAPI: Swagger, ReDoc, OpenAPI JSON
• MCP tool nexus_inbound_webhook_schema returns the same contract for agents (no order placement via MCP)
• Multi labeled endpoints (separate UUIDs per source) are planned; today one primary URL per account

Discord commands

Invite the MrTrades bot, then use slash commands in your server. Linking with /link is for bot trade controls; /support is a separate private ticket.

• Account: /ping, /status, /link
• Support: /support, /support_reply
• Channel posts: /subscribe, /unsubscribe
• Scanners: /fib, /harmonics, /ict, /elliott, /setups
• Desk ticker: /ticker
• Bot trades: Discord bot controls

Ticker Discord

Control a claimed LED ticker from Discord. Layouts and the desk strip also live in Portal under devices.

• /ticker status — layout and desk settings
• /ticker layout — MrTrades, Scanner + desk, Harmonic setups, Bot Overview, Bot Activity, Tape
• /ticker lane — LIVE or PAPER for the trade-desk strip
• /ticker desk — show or hide the desk strip
• /ticker alerts — open/close/stop overlays
• /ticker notice — flash a short message on the board

Scanner APIs

Cached GET plus POST …/scan to refresh. Same setups Discord /fib and friends show. Full schemas in Swagger.

• GET /v1/nexus/scanners/overview
• Fib, ICT, harmonics, Elliott, AMT, smart money — /v1/nexus/scanners/<name>
• GET /v1/nexus/scanners/book-impulse
• Sweep turn — the low is at least 2% under the high of the prior 30 minutes, then a buy of at least $5,000 and at least ten times that pair's usual print from the prior hour. Alerts, a stored-tape replay, and a paper order on the row you choose. GET /v1/nexus/scanners/sweep-turn/scan, /alerts, /strategy, /backtest. The dollar size and the leverage are the ones you enter. Automatic orders use the Nexus lane.

Discord bot controls

Manage your Nexus bot from Discord without touching Terminal positions. Open Nexus bot, create a one-time linking code, then run /link code:<code> in Discord. Leave live management off until you need it. Every live action still needs a second Confirm tap.

• Discord can only see and change trades the bot (or Discord) opened. Positions you open in Terminal stay in Terminal.
• /reduce is capped by your max reduce fraction (default 25%). /close always closes the full bot position, still inside your remote notional cap.
• View: /status, /positions, /orders
• Pause and manage: /pause, /resume, /reduce, /close, /move_stop, /cancel
• Opening a new live trade from Discord (/open, /size, /lev) needs extra permissions. Keep those off unless you specifically want them.
• Emergency revoke in Nexus bot immediately stops pending confirmations.