Connect supported OpenAI or Anthropic API keys from Settings > AI Assistant. OttoTrader does not reuse consumer ChatGPT or Claude website logins.
AI Assistant
AI assistance grounded to OttoTrader strategy rules.
Use OpenAI or Anthropic API keys inside the desktop app, or export OttoTrader instructions for browser-based AI tools. Generated strategies must still pass OttoTrader validation before they can be applied.
AI Strategy SessionGrounded in OttoTrader's strategy contract
Export OttoTrader AI instructions and a priming prompt, upload them into a browser AI session, then bring generated JSON back for local validation.
Generated strategies must match OttoTrader's supported strategy contract before they can be applied.
Capabilities
AI for strategy work, not market prediction.
AI can help draft, revise, explain, and format strategy logic. It does not predict markets, guarantee outcomes, or replace user review.
Turn ideas into drafts
Describe a setup in plain English and let the AI Assistant draft OttoTrader strategy JSON you can review and validate locally.
Revise and understand logic
Ask the assistant to refine strategy rules, compare alternatives, or explain the tradeoffs before you apply changes.
Export browser-AI instructions
Prefer not to connect provider keys? Export OttoTrader instructions and a priming prompt, use them in a browser AI session, then bring validated JSON back into Strategy Warehouse.
Provider API keys
Use OpenAI or Anthropic API keys from their developer platforms inside Settings > AI Assistant. Provider keys are sensitive and should stay out of reports, logs, exports, marketplace listings, and public content.
Browser AI export
Prefer not to connect API keys? Export OttoTrader AI instructions and a priming prompt, upload them into a browser AI session, then bring the generated OttoTrader strategy JSON back into Strategy Warehouse > Code for local validation.
Validation boundary
Generated JSON must obey OttoTrader rules.
Unsupported modes, invented fields, invalid payloads, or generic trading JSON should be rejected or repaired locally before applying. AI confidence is not strategy evidence.
Builder-grounded validation
Generated payloads must match OttoTrader's supported strategy contract before the Visual Builder or live workflows can use them.
Protected strategy boundary
AI Assistant must not reveal protected marketplace internals. Bought protected strategies expose only buyer-safe metadata, permitted tunables, reports, and explanations allowed by the delivery contract.
User review remains required
AI drafts do not replace backtesting, lookahead audit, Demo work, risk review, or the user's decision before Live Real deployment.
Next page
See why testing matters more than AI confidence.
OttoTrader's AI is strongest when every draft still has to pass product rules and validation checks. Testing keeps strategy ideas accountable before they earn trust.