Markets & brokers
This is the single source for which markets Stretus trades, which broker reaches each one, and what each market settles and quotes in. Every other page that mentions a market links here rather than repeating it.
A market having a row in this table means Stretus has reference data for it, sessions, currencies, a calendar, a broker adapter. It does not mean you can trade it today. The Available column is the one that answers that.
Markets
| Market | Venues | Currency | Quoted in | Settlement | Broker | Available |
|---|---|---|---|---|---|---|
| India | NSE, BSE | INR | INR | T+1 | Upstox | Yes |
| Crypto | Binance Spot, Bybit Spot | Quote asset (USDT/USDC) | same | Instant | Binance, Bybit | Yes |
| United States | NASDAQ, NYSE, NYSE_ARCA, NYSE_AMERICAN, CBOE_BZX | USD | USD | T+1 | Alpaca | Pending activation |
| United Kingdom | LSE | GBP | GBX (pence) | T+2, moving to T+1 on 2027-10-11 | Interactive Brokers | No, see below |
| Netherlands | EURONEXT_AMS | EUR | EUR | T+2, moving to T+1 | Interactive Brokers | No, see below |
| Spain | BME | EUR | EUR | T+2, moving to T+1 | Interactive Brokers | No, see below |
| Australia | ASX | AUD | AUD | T+2 | Interactive Brokers | No, see below |
| UAE | DFM, ADX | AED | AED | T+2 | Interactive Brokers | No, see below |
Venue ids are short codes, not MICs. Send NASDAQ, never XNAS. The MIC is a separate field, and for four venues it differs from the operating MIC in a way that cannot be derived. See Venue identifiers.
What "pending activation" and "no" mean
United States, pending activation. Venues, sessions, calendars, currencies and a 100-instrument universe are all in place, and the Alpaca adapter is validated against Alpaca's live paper endpoint. What remains is an operational step: activating the venues and the paper adapter on an environment, then running the order, fill, position, reconciliation and close chain once.
UK, Netherlands, Spain, Australia, UAE (not available. These have venues, sessions, currencies and calendars, and no instruments. That is not an oversight. Interactive Brokers publishes an instrument's minimum price increment only through an authenticated endpoint, and a placeholder tick size is not a gap in the data) it is a wrong tick size on every order, so limit prices are either rejected or mispriced. Seeding them requires an authenticated IBKR session, which requires vendor onboarding.
UAE has one further blocker: no calendar. Eid al-Fitr and Eid al-Adha depend on the Islamic lunar calendar and are fixed by official moon sighting days ahead, so DFM and ADX announce their holidays by notice rather than publishing a computable rule. A generated UAE calendar would be plausible and wrong by a day or two around each Eid. And being wrong by one day is worse than having nothing, because the venue would report itself open on a public holiday.
Which broker reaches which market
| Alpaca | Interactive Brokers | |
|---|---|---|
| Markets | United States | UK, Netherlands, Spain, Australia, UAE (and the US) |
| Credentials | API key + secret | a session |
| Paper vs live | different hostname and key prefix | the same URL, only the session knows |
| Instrument identity | the symbol | an integer contract id (conid) |
| Modifying an order | cancel + replace, so the order id changes | the order id is preserved |
| Fractional shares | yes | no |
Two rows there change what you see in the product.
Alpaca modify is cancel + replace. Alpaca has a real amend endpoint, but using it reassigns the broker's order id. And a reassigned id orphans every subsequent fill, which then arrives and fails to match anything. So a "modify" on an Alpaca order produces a new order with a new id, and the original shows as cancelled. That is the safe behaviour, not a limitation being worked around.
IBKR permits one session per username, across every IBKR service. Web API, TWS, IBKR Mobile. All of them. If you sign in to IBKR Mobile while a strategy is deployed, you take the session from the platform, and the platform will not take it back: re-authenticating would take it from you again, producing an authentication war visible only as intermittent failures on both sides. IBKR's own remedy is a separate username dedicated to API access, and that is the recommendation here too.
Currencies
| Code | Currency | Where |
|---|---|---|
INR | Indian rupee | NSE, BSE |
USD | US dollar | the five US venues |
GBP | Pound sterling | LSE (settlement) |
GBX | Penny sterling | LSE (quotes only, never a balance) |
EUR | Euro | EURONEXT_AMS, BME |
AUD | Australian dollar | ASX |
AED | UAE dirham | DFM, ADX |
GBX is the one that needs care. See Currencies & the GBX case.
Venue identifiers
Each venue carries an ISO 10383 MIC and an operating MIC. For nine of the thirteen venues they are the same code, which is the awkward part: equality looks like a rule, and it is wrong for exactly the venues an external counterparty is most likely to ask about.
| Venue | MIC | Operating MIC |
|---|---|---|
| NASDAQ | XNAS | XNAS |
| NYSE | XNYS | XNYS |
| NYSE_ARCA | ARCX | XNYS |
| NYSE_AMERICAN | XASE | XNYS |
| CBOE_BZX | BATS | XCBO |
| LSE | XLON | XLON |
| EURONEXT_AMS | XAMS | XAMS |
| BME | XMAD | BMEX |
| ASX | XASX | XASX |
| DFM | XDFM | XDFM |
| ADX | XADS | XADS |
| NSE | XNSE | XNSE |
| BSE | XBOM | XBOM |
Regulatory and settlement reporting commonly keys on the operating MIC; venue-level market data keys on the segment. Neither is derivable from the other, so both are stored.
Nasdaq Dubai (DIFX) is deliberately absent: IBKR coverage of it was unconfirmed, and it was left out rather than guessed at.
Indian equity and crypto brokers
The table above covers the global equity venues, which is where the broker question is hardest. Two other groups matter and were previously undocumented.
Earlier docs named "Upstox for Indian equity, and Binance or Bybit for crypto spot" as the supported set. That was the connect screen's two-broker fallback, not the platform's coverage.
The connect screen builds its list dynamically from reference data, filtered to the adapters enabled for your tenant. The platform carries order-placement adapters for more than twenty brokers and exchanges.
Indian equity (NSE / BSE)
Fourteen adapters:
Upstox, Zerodha, AngelOne, Dhan, Fyers, Groww, 5paisa, Sharekhan, ICICI Direct, HDFC Securities, Kotak Neo, Motilal Oswal, Paytm Money, SBI Securities
All route to NSE and BSE. All require per-strategy broker approval before live orders are placed. See Paper vs live.
Crypto
Eleven adapters:
Binance, Bybit, Coinbase, CoinDCX, Kraken, KuCoin, OKX, Gate.io, MEXC, Bitget and Upbit
Separate adapter rows exist for Binance futures and options, and for a Binance testnet endpoint.
Valid API keys plus a live deploy means real orders on the next candle close.
FX
OANDA, the user-facing picker is disabled by default and retail OTC forex is out of scope. See Regulatory position.
Simulation
An internal paper adapter, which is what Stretus paper trading uses. It is not something you connect. See Paper trading.
Why "which adapters exist" and "which you can use" differ
Every broker family seeds a row in a tenant-adapter table, and each row carries an enabled flag. Adding a broker is adding data rather than code, and enabling one for a tenant is a reviewed change rather than an invented insert.
The pattern is deliberate, Alpaca ships with its paper adapter enabled and its live adapter disabled, so "not enabled" is expressed by a flag on an existing row rather than by a missing row. Which means a broker you cannot see is not enabled for your tenant, not absent from the platform. See Plans & entitlements.