The loop is easy to describe: fetch candles for a watchlist, compute indicators, ask a model for a Buy, Sell or Wait read with levels and a reason, and alert when it changes. An agent builds a personal version in a sitting. The hard part is data, not code: crypto candles are free from exchanges, while real-time stocks, forex and futures are licensed. A home-built read also has no track record behind it, so treat what you build as a research notebook, not advice; the product itself says it provides analysis and places no orders.
Before you buildTradingWizard has no free plan, but TradingView's free plan covers charts and a few price alerts if that is all you need.
Build me a personal market watch to replace TradingWizard for a short list of assets. Requirements: - Node.js 22 + TypeScript: a Fastify API and a React UI built with Vite. `npm start` serves http://localhost:5400 and runs the scanner in the same process. - Storage: better-sqlite3 in ./data/watch.db: watchlist (symbol, market crypto or stock, timeframe 1h / 4h / 1d), candles, reads (time, label Buy / Sell / Wait / Avoid, entry, stop, target, a two-sentence reason, model name) and alerts sent. Keys and settings are in .env. - Data behind one CandleSource interface: crypto candles from a public exchange endpoint through `ccxt` (no key); stocks through `yahoo-finance2` (unofficial and possibly delayed, so say so in the UI). If the newest candle is older than twice the timeframe, skip the scan and show "data stale". - Indicators computed in code with `trading-signals`: EMA 20/50/200, RSI 14, ATR 14, MACD, volume against its 20-bar average and the nearest swing high and low. The model receives this table, never raw prices. - Reads: per item on its own schedule (`node-cron`; crypto around the clock, stocks while the exchange is open), send the table to an LLM from .env (ANTHROPIC_API_KEY, OPENAI_API_KEY or OLLAMA_URL) and require JSON validated with `zod`. Replace a read with Wait when its stop is on the wrong side of the entry or its levels sit more than 3 ATR from the last close. - Paper ledger: a Buy or Sell read opens a simulated position that closes at its stop or target using later candles; show closed trades, wins and losses per symbol, losses included. Simulated only: no broker or exchange fields exist anywhere in the app. - Alerts when a label changes, through ntfy (NTFY_TOPIC) or a Telegram bot (`grammy`). Every screen and alert carries "Analysis, not financial advice. Simulated trades only." - UI: watchlist table with label, levels, reason and age; a symbol page with a candle chart (`lightweight-charts`) and its history. No accounts, no telemetry, local-first; outbound calls go to the data source, your LLM and your alert channel. - Out of scope: real orders, futures and forex feeds, a mobile app, copy trading, performance claims. - README: setup, data caveats and terms of the unofficial feed, the cost of one scan, and a warning that nothing here has a proven edge: test before relying on any read.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own TradingWizard.
Add a backtest to the market watch app in this folder. Requirements: - A command `watch backtest <symbol> --from <date> --to <date>` that replays stored candles bar by bar, using only data up to each bar, and applies the same indicator code. - Use a rule-based stand-in for the LLM (the label comes from EMA and RSI thresholds in config), not live model calls, and say so in the output. - Report trade count, win and loss counts, average win and loss in ATR units, maximum drawdown and the buy-and-hold change over the same period, with fees and slippage set in config. - Print a warning that past results do not predict future ones. - Update the README.
Add a daily digest to the market watch app in this folder. Requirements: - At a time in the timezone from .env, send one message through the existing alert channel: each watchlist item with its current label, how long it has held it, and any change in the last 24 hours. - Skip items with stale data and list them separately. - A setting to switch per-change alerts off when the digest is on. - Keep the "Analysis, not financial advice. Simulated trades only." line in the message. - Update the README.
Add a model comparison to the market watch app in this folder. Requirements: - Configure a second LLM in .env and run both on every scan, storing each read with its model name; only the primary model's read triggers alerts. - A page that shows, per symbol, where the two labels agree or differ, and the token cost of each. - A weekly count of agreement and of rejected reads per model. - Update the README.
People pay to have the assets they follow checked on a schedule, with the levels and the reason written out, without wiring data feeds and prompts themselves. It stays a tool for analysis: the product says it places no orders and that every decision is yours.
Estimate · Crypto data is free and ntfy is free. The LLM costs cents per scan through an API, so ten assets on an hourly schedule add up to a few dollars a month, or nothing with a local model. The build is token usage on your agent plan.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Pro | $40 | $29 | 5 demo bots (paused ones count), 10 alerts, unlimited chat with its assistant, 2,000 analyses a month and 5 live web checks a day, with a REST API and MCP connection listed on the pricing page. |
No free plan, only a 7-day trial that needs a card; $0 is charged today. You can browse without a plan.
Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Licensed live data across stocks, ETFs, futures, forex and crypto in one place, The iPhone app and its phone alerts.
About $40 a month on the Pro plan, $480 a year (checked 2026-10-19).
Licensed live data across stocks, ETFs, futures, forex and crypto in one place; The iPhone app and its phone alerts; A public page with each of its own bots' closed demo trades, losses included; The REST API, webhooks and MCP connection to AI tools such as Claude and ChatGPT; Chat about any asset with live web checks. If any of those matter to you, keep paying.
Yes: TradingAgents (open source), AI Hedge Fund (open source), Freqtrade (open source).