TradingView alerts, executed on your own exchange keys.

TensorTrader meters concurrent technical alerts, not how many times they fire in a month. Essential is 20, Plus is 100, Premium is 400, and Ultimate is 1,000. Batch Create writes a reviewed plan from the tickers, accounts, studies, and timeframes you pick, then reconciles your TradingView account for duplicates. That is create-once plus cleanup, not an exactly-once guarantee if you also click Create Alert by hand. TrendSpider and GoCharting keep their own vendor caps; we do not raise them. Free is one token, one timeframe, and one exchange with no card. If you already have alerts, the plan shows what would be created, skipped, or replaced before anything is written.

A webhook is not an order until it passes the bridge. TensorTrader allow-lists the command keys, rejects replayed payloads, normalizes the symbol to the venue you selected, and clamps leverage to the lower of your policy and that venue’s published max. Sizing uses the account value and risk settings you configured — not a hidden default. Interactive Brokers confirmation handshakes fail closed if the reply is unexpected. DEX venues use a trade-only agent key. The adapter then sends a native venue order (market, limit, reduce-only, or close) instead of a generic wrapper. If the confirmation is ambiguous, the engine stops rather than guessing a fill.

After a fill, TensorTrader records the venue order id and reconciles position state on a fail-closed path. ATR stops and take-profit are software-side unless the venue acknowledges a native bracket. A liquidation-aware clamp keeps isolated-margin stops inside the venue liquidation price. Account-level capital protection can flatten or pause when a daily loss latch trips. None of this is a guarantee of fill quality, stop execution, or profit: if the venue is down, a software stop cannot fire. You watch the HUD for open positions, recent fills, and rejected webhooks. Ambiguous venue replies stay unresolved instead of being booked as wins.

Every new venue starts in paper or testnet. A stored API key is configuration, not permission to trade live. Live enablement is an explicit opt-in after a credential preflight that checks trade-only scope and rejects withdrawal-capable DEX owner seeds. Pioneer trial users can unlock all exchanges for 90 days; after that, slots return to the scope locked at checkout. Interactive Brokers starts on a DU paper account. Alpaca starts on paper and keeps live crypto entries gated unless you opt in. You can cancel a Stripe trial before it ends and pay nothing. The same alert contract is used in paper and live so the only change at flip is the venue environment, not the payload shape.

No. Balances stay on the exchange, DEX, or broker you already own. TensorTrader stores only the credentials required to place and cancel orders: trade-only CEX API keys, or a restricted DEX agent key. We never need a Hyperliquid or Lighter owner seed, and we do not store withdrawal-capable keys. Card numbers are entered on Stripe-hosted checkout and never reach our servers. You can delete the stored key from Settings at any time; that does not close positions on the venue. Support is support@agent-swarm.net. The Terms, Privacy, and Refund pages are the legal record; this answer is the operational one.

Community scripts climb a 15 → 30 → 60 → 240 minute ladder on BTC, ETH, and SOL perps. Scores are median per-symbol ROI and Sortino plus worst drawdown — not pooled compounding. ROI is sum-of-trade and fee-aware: about 14 basis points per round trip compounds to roughly −75% over 1,000 trades, so a script that looks profitable on TradingView’s headline net can still rank poorly here. TT-Autotune champions are walk-forward genetic fits versus a stock Lorentzian baseline, with CPCV sign-stability checks before a cell is treated as trained. Dated boards on this page are research evidence from stored tapes. They are not expected live performance, and Agent V2 paper/live flags remain off.

No. A TradingView, TrendSpider, or GoCharting alert webhooks to TensorTrader. We validate the payload, size the order, and send it with the venue’s native semantics on keys you already own. The listener runs in our cloud. Your laptop can be closed. The stack many traders still use is the opposite: the charting site fires a webhook at a MetaTrader Expert Advisor on a Windows VPS you rent and babysit. That box must stay logged into the broker, accept inbound HTTPS, keep a correct clock, and survive patch reboots. When the VPS updates, the RDP session drops, or the EA crashes, alerts queue or vanish and you notice after the move. You pay that VPS bill on top of the charting product and the EA. A browser-extension executor has the same “leave the machine on” problem unless the vendor sells a separate always-on cloud. We are that cloud: no RDP, no EA process to restart, no second hosting invoice for execution.

No. Agent V2 does not place paper or live orders. Today it is a research program: signed target-notional experiments, Kronos / HMM / hybrid bake-offs, held-out slices, and CPCV sign-stability. Those jobs exist to decide whether a sizing policy is stable enough to trust. Dated bake-off numbers on this site are evidence from that work, not a live book and not expected performance. If the gates pass, later deployment follows the same three jobs you already have. Create stays your alerts — V2 does not invent a new signal source. Build would mean proposing a size on the existing fail-closed bridge, not bypassing allow-lists or leverage clamps. Monitor would mean shadowing a fill and flagging a policy breach. The sequence is paper first, then an explicit live flag, never a stored credential implying permission. Premium shadow and Ultimate enforce oversight are the shipped products on that path; they are not Agent V2 and they do not turn V2 on.

TrendSpider-only or GoCharting-only is half the selected TensorTrader plan, currently $10–$90 per month. That is our execution fee, not their charting subscription. You still pay TrendSpider or GoCharting for their product. We do not raise their vendor caps: TrendSpider stays on their Standard–Advanced bot and alert limits (5 bots / 10 alerts on Standard, up to 100 bots / 400 alerts on Advanced, with their expiry windows). GoCharting stays on their paid webhook cap — 100 price/delta alerts and 5 indicator alerts — on every TensorTrader tier. What you get from us is the same bridge a TradingView user gets: webhook intake, allow-listed commands, symbol normalization, leverage clamp, sizing from your settings, native venue orders, HUD positions and fills, and capital protection. Batch Create in the Chrome extension is TradingView-specific; on TrendSpider and GoCharting you keep building the alert on their chart and we execute it. TradingView on our plan is full price because we also enforce the 20 / 100 / 400 / 1,000 concurrent technical-alert slots. Add two providers and both weights apply (TradingView full plus TrendSpider or GoCharting at half).