Getting Started
Quickstart
Build and deploy your first trading bot in minutes. Start with paper trading to validate your strategy before going live.
Before you start
Steps
Create your Argix Labs account
Sign up at the registration page. You'll need to agree to the Terms of Service, Privacy Policy, and Risk Disclosure Statement.
Connect your Broker
Navigate to Settings > Broker Connections and link your brokerage. Follow the prompts for your broker—often API keys with trading permissions, or secure sign-in where OAuth is supported.
Build your first bot
Open the Bot Builder. You can wire up signals, filters, entries, exits, sizing, and risk controls as you go—the canvas gives you options for each part of the strategy without locking you into one path on day one.
Backtest your strategy
Run a backtest against historical data. Review performance metrics. Remember: backtesting results are hypothetical and do not guarantee live performance.
Deploy to paper trading
Deploy your bot in paper trading mode first. Monitor performance and behavior before committing real capital.
Go live (when ready)
Once you're confident in your strategy, switch to live trading. The platform will submit real orders to your brokerage account using the logic you configured.
Broker account & API access
Most broker integrations need credentials from your broker's developer or security settings—often a public API key plus a secret or private key, or an OAuth flow instead of pasting secrets. Enable trading (not read-only) when you intend to place orders. Exact labels and steps differ by broker; use their docs alongside Argix Labs.
API Key: XXXXXXXXXXXXXXXXXXXXXXXXSecret Key: ********************************Capabilities you usually need: - Account / balances (read) - Order placement (trade) - Quotes or market data (as offered by the broker)Tip: Paper, demo, or live endpoints often useseparate keys—start with paper when available.How the builder stays organized
The builder incrementally constrains the strategy graph toward structural completeness. The runtime classifies nodes into seven component types (table below); validation and deployment checks enforce consistency with that schema during backtest and live execution.
| Component | Min Required | Purpose |
|---|---|---|
| Signal | One or more | When to look for an entry |
| Filter | As needed | Extra gates (time, regime, volume, etc.) |
| Entry rule | Usually one | How orders are sent (market, limit, stop) |
| Exit rule | One or more | Stops, targets, trailing logic |
| Position sizer | Usually one | How size is chosen per trade |
| Risk management | One or more | Portfolio and per-trade guardrails |
| Universe | As needed | What symbols or lists the bot considers |
Important risk warning