KAS strategy
EMA Crossover
XAUUSD · M5 · 0.10 lots
onBar()RunningLogsSettings
Koneth automatic trading
Your strategy.
Run it your way.
Build and run a KAS inside the native macOS or Windows terminal, or connect your own backend through the account-scoped Trader API.
Desktop KAS · External API integrations · Account-scoped execution
KAS / Desktop terminal Connected
Koneth Automated StrategiesEMA Crossover
runningCREATEKS editor
CONFIGUREInputs
MONITORLogs
onBar EMA crossoverAuto Trading on
const fast = ema(close, 20);const slow = ema(close, 50);if (crossover(fast, slow)) { trade.buy({ volume: 0.10 });} Running · XAUUSD · M5Open logs
KS editorAuto Trading controlsTrader API / v1
KAS in Koneth Terminal
Build it. Run it.
Right where you trade.
Koneth Automated Strategies run locally inside the native macOS and Windows terminals. No separate backend or API credentials are required to create and operate a KAS.
Automation workspace
Koneth Automated Strategies
Auto Trading+ Add KAS
Strategies2 saved
Runtime1 running
Account10002341
KAS strategy
Breakout Guard
EURUSD · H1 · 0.05 lots
onTick()StoppedEditStart
Create or import a strategy
Write a strategy in the KS editor, validate it before saving, or import an existing .ks file.
Configure every run
Review the symbol, timeframe, volume, and strategy inputs before automated trading begins.
Control trading twice
Use the terminal-wide Auto Trading switch and a separate permission for each KAS.
Monitor the runtime
See running status, inspect logs, change settings, export the strategy, or stop it immediately.
KAS is available in the native macOS and Windows apps. Stopping a strategy stops future actions but leaves its existing positions open for you to manage.
The Trader API flow
One account-scoped API.
A complete automation loop.
Your strategy runs in infrastructure you control. The Trader API provides account state, position execution, and replayable events from the trading server.
POST /v1/auth/loginCreate an account-scoped session
Connect your trusted backend or native client to one trading account on one Koneth trading server.
POST /v1/tradeSend idempotent trade actions
Open, close, or modify a position. Give each intended open action a unique client_request_id so retries stay safe.
GET /v1/streamStream events and reconcile
Resume from your last cursor after reconnects. If replay is truncated, refresh the source of truth with GET /v1/positions.
Trader API v1 surface
Five endpoints.
One automation loop.
POST/v1/auth/loginCreate a session for one trading account and server.
GET/v1/accountRead balance, equity, margin, and access state.
GET/v1/positionsRead the authoritative open-position snapshot.
POST/v1/tradeOpen, close, or modify a position.
WS/v1/streamReceive replayable order and position events.
Strategy examples
Your signals.
Run your way.
Build EMA, RSI, breakout, momentum, trend, or grid logic as a desktop KAS—or bring the same strategy model to your own Trader API backend.
These strategies are illustrative signal models. Review every KAS or API integration, its sizing, symbol rules, and risk controls before enabling live trading.
Automation safety
Control stays
with the trader.
KAS and Trader API integrations use the normal Koneth execution path, but you still own the strategy rules, permissions, sizing, and monitoring.
Review every strategy
Check a .ks strategy, its editable inputs, symbols, timeframes, and volume before you allow it to trade.
Use both KAS permission gates
The terminal-wide Auto Trading switch and the per-strategy Allow automated trading control must both be enabled.
Keep API credentials server-side
Trader API session tokens belong in a trusted backend or native client—not browser code or public repositories.
Build API retries for safety
Use idempotent open actions, process replayable events durably, and reconcile against authoritative server state.