From a broker connection to a live bot

Pick a broker in the app and you land on that broker's authorization page, on the broker's domain. You log in there, approve the scopes Nyria asks for, and the broker hands back an access token over a server-to-server callback.

Schwab, tastytrade and live Tradier accounts use OAuth 2.0. Alpaca and Tradier's paper sandbox use API keys you generate in the broker dashboard and paste in. Either way the credential lands in access-controlled storage that only the order path reads, and /security says which parts of that aren't hardened yet.

Alpaca and Tradier run their own paper environments. Schwab and tastytrade are live-only at the broker, so Nyria attaches a simulated account to every signup instead. You can put a strategy end to end through that before connecting any broker at all.

Every strategy gets its own webhook URL and a token. Anyone holding the token can fire alerts at that strategy; anyone without it gets a 401 at the edge. Tokens belong to the strategy rather than the account, so you can rotate one source without disturbing the others.

Choose the source up front: TradingView, a channel in a Discord server you run (bot messages included), or a plain webhook from anything that can POST. Telegram is in the picker with a coming-soon label and can't be selected yet.

Send it the alert you already write. "BTO SPY 450C 6/19 x5" comes out the far side as a structured options order, and strict JSON works just as well. There's no template to match.

Paste a sample alert, or pick one this strategy already received, and it goes through everything a real alert goes through: the symbol, the contract, the size, the trading window, and whether the broker on the other end can place it.

The symbol is resolved against your broker's universe. Option contracts are mapped to OCC symbols and checked against the live chain. Size is computed from your account as it stands now. Trading windows, position caps and account halts are evaluated against live data, and anything the broker can't do is refused here rather than at fill time.

Every alert and every decision lands in the log. A rejected order says which check rejected it and why, and you can re-run any past alert to see what today's account state would do with it.

Size per bot, set on the deploy step: a dollar budget the bot spends each time the strategy fires, or an exact number of units. A budget becomes a quantity at the price when the alert lands, not the price when you deployed.

Instruments narrow what the bot may touch. Scope it to one ticker, a watchlist, or everything the strategy emits. A signal on a symbol outside that list is skipped and logged rather than placed. Crypto bots work the same way, down to a single pair.

Live or paper is the broker account a bot points at, changed from its Account step. To run both on one strategy, deploy a bot for each: Clone opens the deploy form with that bot's sizing and instruments already filled in, and you pick the account. Every bot keeps its own log.