AiXQuant
BTC/USDT PERP ETH/USDT SOL/USDT
Risk-First
Signal map 64.8%
Long +1.20R
No trade
Paper queue Paper
BTC long setup Trigger 67,920
Laddered exits 3 targets
Trade risk -0.80%

Local AI futures trading console

AiXQuant

Built for Windows desktops, AiXQuant brings exchange feeds, AI strategy services, execution controls, and a unified trade database into one operator-facing console for research, paper trading, and tightly supervised live deployment.

Market data REST + WebSocket Warm start candles, incremental updates, reconnect logic, and local gap recovery.
Strategy layer Multi-factor judgment Trend, structure, momentum, derivatives, headlines, and account context.
Risk gate No-Trade Filter No execution when the setup is late, incomplete, or fails account-level controls.
Deployment Local desktop 127.0.0.1 by default, with no public trading API exposed unless you choose to.
Decision pipeline

From market context to an executable trade plan

AiXQuant does not convert raw AI text directly into orders. The stack assembles market state, indicators, headlines, account exposure, and runtime health before producing a structured plan with entry, stop, targets, and explicit veto reasons.

01

Market and state intake

REST bootstrap data, WebSocket deltas, and local SQLite snapshots keep views aligned.

02

AI strategy synthesis

Candle structure, momentum, volume, derivatives, headlines, and open exposure become one auditable context.

03

Judgment and veto

Direction, entry, stop, target, and no-trade rationale are all pushed through risk validation.

04

Controlled execution

The AiXQuant engine handles REST, WebSocket, and local scheduling while preserving logs and order history.

Desktop modules

Real features built around an operator workflow

Start with market and position monitoring, move into plan review, and finish with supervised execution and replay.

Charting workstation

Multi-timeframe charts, MA/EMA/BOLL/MACD/RSI, crosshair tools, drawing, and export.

Execution control

Start, stop, restart, API checks, and runtime state from a single desktop surface.

AI trade plans

Turn direction, trigger, stop, target, and no-trade logic into traceable plans.

PnL and position review

Trade history, floating PnL, equity curves, and order outcome charts for replay and review.

News intake

Market headlines and event context can flow into the AI analysis layer instead of staying isolated.

Configuration workspace

Form editing, JSON validation, backup and restore, and app-level AI settings in one place.

Risk before speed

Control downside first, then talk about upside

The platform is designed to block incomplete or low-quality setups before they reach execution. Late entries, invalid stops, API issues, position pressure, and data gaps all become hard pre-trade checks with visible veto records.

Late-entry filter Blocked
Max loss / trade -0.80%
API exposure 127.0.0.1
Trade release Manual confirm
Architecture

Desktop console + AiXQuant engine + AI services

The local console owns configuration, monitoring, veto logic, and replay; the AiXQuant engine owns runtime trading processes and REST/WS access; AI services generate analysis and trade plans.

AiXQuant Desktop
AiXQuant Engine
AI Strategy Services
SQLite Trade Store
OKX Binance Bybit adapter Public feeds
Product Q&A

Operating boundaries and market access

These rules define when the platform generates an executable order and when it intentionally stands aside.

01How does AiXQuant decide whether to trade?

The stack classifies the market, builds a candidate plan, and lets local risk logic decide if it can be executed. AI can propose direction and logic, but only a validated final plan can move forward.

02Why focus on intraday setups instead of broad directional calls?

The current system is tuned for short-cycle futures execution. It uses 15m for timing, 1h for the session frame, and 4h for structural risk boundaries, instead of wrapping overnight directional opinions into an order.

03What happens when price is not inside the valid entry zone?

If price is late, the stop is not structurally valid, or reward-to-risk fails the threshold, the platform returns WAIT or NO_TRADE. That is a normal strategy outcome, not a system failure.

04Which exchanges are currently supported?

OKX is the primary strategy-market source today, Binance can serve as public-feed backup, and Bybit plus additional venues are adapted version by version. Confirm API scopes, contract types, and market coverage before live deployment.

Local deployment

Built for paper-trading validation before live capital

AiXQuant is best used as a local research, simulation, and supervised trading console. Before routing real orders, isolate API permissions, prove the workflow in paper mode, confirm risk thresholds, and test with small size.

Back to top

Risk disclosure: nothing on this page is investment advice or a return guarantee. Futures trading is high risk, and backtests, simulations, and historical data do not predict future performance.