signals
Listening to Trading Signals with sn signals
sn signals subscribes to the live NATS signal stream and prints one JSON object per signal to stdout. This is the primary input loop for a trading bot agent.
Prerequisites
sn must be installed and configured:
# Install
brew tap spot-canvas/sn https://github.com/Spot-Canvas/sn
brew install spot-canvas/sn/sn
# Configure (only needed if pointing at a non-default server)
sn config set api_url https://signalngn-api-potbdcvufa-ew.a.run.app
No NATS credentials setup is needed — sn signals uses embedded read-only credentials by default.
More from spot-canvas/sn
sn
Use the sn CLI to manage the SignalNGN platform. Covers products, backfill, backtests, trading config, user strategies, strategies, ML model reloads, metrics, engine status, tenants, live signal streaming, and live price lookup. Use sn instead of curl for all API operations.
9openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
7trading-bot
Build a signal-driven cryptocurrency trading bot using the `sn` and `ledger` CLIs. Covers the full loop — signal consumption, strategy filtering, trade execution, position sizing, risk management (SL/TP, trailing stops, max hold), and position monitoring. Use when implementing a trading bot, adding risk management to an existing bot, or understanding the signal-to-trade architecture.
7openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
7openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
7openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
7