Live execution, protected by explicit confirmation and risk controls

Broker connection

A user connects a supported broker account through that broker’s API. The platform tests the connection and synchronizes account, position and funds data before marking the broker as connected. API credentials are handled through secure secret management and are never exposed to browser-side code.

Before a strategy can trade live

• An explicit risk acknowledgment from the user
• A tested, active broker connection
• Configured risk limits for that strategy
• Manual start of the strategy — nothing runs automatically without this step

Order & state management

• Order lifecycle tracking: pending, submitted, open, filled, partially filled, rejected, cancelled, failed
• Client-generated order IDs mapped to broker order IDs for traceability
• Duplicate-order prevention and idempotent order processing
• State reconciliation after a connection loss, so positions stay accurate
• A clear LIVE indicator shown throughout the interface whenever real capital is at risk

Safety behavior

If a broker API, market-data feed or internal service becomes unavailable, the platform is designed to fail safe — stopping new order placement rather than guessing — and to alert the user. A global emergency kill switch can halt all live strategies immediately.

Important disclosure

Live trading risks real capital. my ALGO agent provides the software and broker-connectivity architecture; it does not custody funds, guarantee execution quality, or provide personalized investment advice. See Risk Disclosure.