How Nyria works

Connecting a broker on Nyria starts at app.nyria.io/integrations. Pick a broker and you are redirected to that broker's authorization page, hosted on the broker's domain. You log in there, approve the scopes Nyria requests, and the broker returns an access token and refresh token to Nyria over a server-to-server callback.

Schwab, tastytrade, and TradeStation use OAuth 2.0. Tradier, Alpaca, and Binance use API keys you generate inside the broker dashboard and paste into Nyria. Coinbase uses JWT-signed requests against Advanced Trade. In every case, credentials sit in encrypted columns and only the trade-bot and order-execution paths can decrypt them.

Paper and live accounts are first-class. Alpaca, Tradier, Binance, and TradeStation expose dedicated paper environments. Schwab, tastytrade, Coinbase, and Webull are live-only at the broker, so for those Nyria attaches its own paper broker the moment your account is created. You can place a strategy against paper before a single dollar of risk goes through your real account.

• OAuth 2.0 — Schwab, tastytrade, TradeStation
• API key — Tradier, Alpaca, Binance
• JWT — Coinbase Advanced Trade
• Paper, live, or both, on the same account

Every strategy you create gets a unique webhook URL and a token hash. The hash is the secret half of that URL. Anyone holding it can fire alerts at this strategy — anyone without it gets a 401 at the edge. Tokens are bound to the strategy, not the account, so you can rotate them per source without disturbing the rest of your setup.

Pick the alert source format up front: TradingView (Pine Script alerts and price levels), Discord (read a channel, including bot messages), Telegram (groups and private channels), or a custom webhook (any platform that can POST JSON). The strategy holds the parsing rules so that whatever shape the incoming alert takes, Nyria knows how to turn it into an instruction.

Plain-text alerts are accepted. The AI parser turns a message like "BTO SPY 450C 6/19 x5" into a structured options order. If you prefer strict JSON we accept that too. There is no single required template — that is intentional.

• Per-strategy webhook URL with a rotatable token hash
• TradingView, Discord, Telegram, custom webhook
• Plain-text or JSON — no required template
• Multi-bot fan-out: one alert, many bots, many accounts

The validation page sits between an alert arriving and an order being placed. Paste a sample payload — or pick from recent alerts received on this strategy — and Nyria runs it through the same pipeline an inbound webhook would hit: parse, symbol resolution, instrument lookup, position-sizing math, risk rule checks, and broker capability gating.

What gets checked is explicit. Symbol is resolved against your broker's universe and any locale or fractional rules. Option contracts are mapped to OCC symbols and validated against the broker's chain. Position size is computed against your current account state. Risk rules like trading windows, max position count, and account-level halts are evaluated against live data. Broker capabilities such as multi-leg orders or perpetuals are gated up front, so a strategy that requires something a broker cannot do never silently breaks at fill time.

Every alert and every decision lands in the audit log. If an order is rejected, the log says which check rejected it and why. You can re-run any historical alert against the same strategy and see whether today's account state would have produced the same result.

• Symbol resolution against the broker universe
• Option contract validation against the live chain
• Position size, risk rules, and account state checks
• Broker-capability gating before order placement

Position sizing is per bot. Choose percent of account equity, a fixed dollar amount, or a fixed quantity. The math runs on the account snapshot at alert time, not at deploy time, so a bot sized at 10% of equity scales with the account as it moves.

Instrument selection narrows what a bot is allowed to trade. A bot can be scoped to a single ticker, a watchlist, or every instrument the strategy emits. If a strategy fires on a symbol the bot is not allowed to trade, the order is skipped, logged, and never placed. Crypto bots get the same treatment — a bot can be locked to BTC-USD spot, every Coinbase perpetual, or a curated set.

Going live versus paper is a toggle on the bot, not a redeploy. The same bot can be cloned to a paper account with one click, and that paper bot's audit log gives you a clean separation between testing and trading. Most accounts run two or three paper bots in parallel with one live bot per strategy.

• Percent of equity, fixed dollar, or fixed quantity sizing
• Per-bot instrument allow-list
• Live and paper bots run side-by-side
• Cloning preserves the strategy, swaps the account