Instrument reference
Symbol formats, timeframes, backtest depth and what you need connected. Which markets exist, which broker reaches each one, and what each settles in now lives on one page: Markets & brokers.
This page used to carry its own markets table. It was one of four, they disagreed with each other, and each was edited separately. There is now one.
Supported instruments
Equity cash
Markets, venues, currencies, settlement cycles and which broker reaches each: Markets & brokers. Sessions and holidays: Trading hours & holidays.
India (NSE, BSE) is available today with roughly 107 symbols. The United States has a 100-instrument universe seeded and is pending activation. The UK, Netherlands, Spain, Australia and UAE have venues and calendars but no instruments yet. See the availability column on the markets page for why.
Crypto spot
- Exchanges: Binance Spot, Bybit Spot
- Settlement: Quote asset (USDT, USDC, or BTC depending on pair)
- Session: 24/7 continuous
- ~104 pairs supported (BTC, ETH, SOL, BNB, and others)
Symbol format
| Asset class | Format | Examples |
|---|---|---|
| Equity | {TICKER}_SHARE | TCS_SHARE, RELIANCE_SHARE, AAPL_SHARE |
| Crypto | {BASE}/{QUOTE} | ETH/USDT, BTC/USDT, SOL/USDT |
The AI accepts both the formatted symbol and common short forms - typing TCS, Reliance, AAPL or ETH in the strategy builder is recognised automatically.
The same ticker can exist on more than one market, and a bare ticker carries nothing to tell them apart. Pick the instrument from the builder's asset selector rather than typing a symbol you assume is unique, the selector resolves it against a specific venue, and that resolution is what everything downstream depends on.
This is why a symbol suffix is not a substitute. Yahoo-style suffixes (.NS, .BO) happen to identify the two Indian exchanges and nothing else, so they cannot express a US, UK, EU, Australian or UAE listing at all.
Supported timeframes
| Label | Candle duration | Typical use |
|---|---|---|
1m | 1 minute | High-frequency intraday |
5m | 5 minutes | Intraday |
15m | 15 minutes | Intraday / swing |
1h | 1 hour | Swing |
4h | 4 hours | Swing / position |
1d | 1 day | Position / trend |
Backtest data availability
This table previously stated "Equity: up to 2 years of daily OHLCV" and "Crypto: up to 1 year of 1m OHLCV." Both figures were wrong and the asymmetry between them did not exist.
| Backtest depth | |
|---|---|
| Every asset class, every timeframe | From 1 January 2024 to now, currently about two and a half years, and growing |
The floor is a single data-availability boundary shared by equity, crypto and derivatives, at every timeframe. The platform stores 1-minute OHLCV and the engine resamples upward, which is why any well-formed interval from 1m to 1d works rather than only a preset list.
A start date before the floor is rejected with the earliest supported date named. It is not silently clamped. See Choosing a test period and Historical data
Backtests use the venue's own trading calendar and session length, so an Indian session is 375 minutes and a US regular session is 390. A backtest run on the wrong session length silently changes the bars-per-day and therefore every intraday holding cap.
Broker connection requirements
| Market | Paper | Live |
|---|---|---|
| India | None - paper runs without a broker | Upstox account connected via OAuth under Profile |
| United States | None | Alpaca API key + secret under Profile |
| UK, NL, ES, AU, UAE | None | Interactive Brokers, not yet available, see Markets & brokers |
| Crypto | None | Exchange API key with trading permissions added under Profile |
Paper trading never needs a broker connection on any market. Note that an Alpaca paper account is a different thing from Stretus paper trading: Stretus paper simulates fills internally with no broker round-trip, while an Alpaca paper account is a real broker account that issues real order ids and settles nothing. Both are safe; only the second one places an order that leaves the platform.