Request definitions for included trades, gains, losses, costs, and measurement periods. We supply the strategy and guide your setup through ChatGPT or Claude. Choose fully autonomous trading or approval before each trade. In autonomous mode, the AI executes without a separate permission request each time.

What to establish before you start

Turn a vague performance statement into specific evidence questions.

Ask for a consistent measurement basis

A useful performance discussion identifies the reporting period, the trades counted, the treatment of losses and costs, and the basis of any return calculation. Keep those definitions stable when comparing periods or products. A selected screenshot cannot supply the missing account history, and a testimonial cannot substitute for a methodology. Bring specific questions to us so a historical figure remains a clearly defined piece of information rather than a promise about your next decision.

Make the agreement understandable before starting

Review the arrangement as a whole: what we supply, what you authorize, what remains your responsibility, and how billing and support work. Bring specific questions rather than accepting an unfamiliar term because the overall offer sounds attractive. A useful agreement should match the workflow you intend to use. Keep the explanation available so later changes can be compared with what you understood at the start, especially when your execution mode or operating environment changes.

Check the complete combination

Compatibility is a question about the actual combination you intend to use: wallet, network, assets, venue, and execution arrangement. Our examples include MetaMask, Phantom, Hyperliquid, Aster, Uniswap, and PancakeSwap. A familiar name on that list is a starting point for the setup discussion, rather than proof that every configuration is identical. Bring your intended combination to us and confirm the practical requirements before moving funds or enabling permissions.

A customer experience to consider

Read Aaron Langley’s original account.

“I wanted to get away from trusting a black box because its interface looked sophisticated. What made the difference was checking approval boundaries and wallet activity rather than the sales demo. The system earned its place because I could inspect the important steps. I do not want to oversell my experience: an attractive AI answer is not verified market data.”
Aaron Langley · · Review 1142
Read the original review ↗Individual experience; not a forecast of your results.

Distinguish a simulation from live use

A backtest evaluates rules against a historical setup with assumptions about execution and costs. Live activity introduces the actual operating environment, venue conditions, and decisions made during the period. Compare each kind of evidence for what it can establish. A simulated result does not become a live record because its chart looks convincing, and a short live trial does not become a long-term performance study. Keep the evidence labels attached when discussing either with us.

Read the experience for what it establishes

A customer's account can show what changed in their own routine, how they experienced setup, or what they found useful. Preserve that personal context when reading it. An experience with support does not prove a return, and one person's reported result does not establish a result for another account. Our archive keeps each review's attribution, date, source, consent, and verification status so you can follow the original account rather than rely on an expanded marketing interpretation.