Compare venue-related operational risk with the distinct question of sending funds to the software provider. 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.

Compare the responsibilities

Evaluate two different risk boundaries without collapsing them.

Compare the custody boundary first, then examine the venue and product independently. Not depositing capital with us addresses who holds funds; it does not settle every consequence of decentralized execution. The comparison should preserve both questions instead of treating one reassuring feature as a complete risk assessment.

Keep the custody arrangement clear

You do not deposit your trading funds with us. Your capital stays within your customer-controlled wallet arrangement, and you retain wallet control and signing authority. That removes the need to hand the software provider custody of your trading capital. It does not remove the risks of a trade, a permission, or a trading venue. Evaluate the custody boundary alongside the strategy and operating setup, rather than treating it as a substitute for understanding them.

Keep location labels precise

Funds can remain customer-controlled while operating software uses a local or cloud arrangement. Storage of capital and location of software are different questions. Ask what each label means in the proposed setup instead of assuming they move together.

Give the trading budget its own boundary

An existing wallet balance is not automatically a trading budget. Distinguish capital you deliberately make available for trading from long-term holdings, household reserves, or business funds. That distinction helps you understand what a proposed trade would expose and whether another position duplicates a risk you already hold. Discuss the intended boundary during setup. More convenient execution should help you follow a deliberate allocation, rather than make every available asset feel like money that needs to be traded.

A customer experience to consider

Read Matthew Greenwood’s original account.

“The problem I kept coming back to was handing responsibility to people who described my account as their property. What matters is that I can stop using a service without asking it to release a wallet it never held.”
Matthew Greenwood · · Review 1187
Read the original review ↗Individual experience; not a forecast of your results.

Treat a mode change as a new decision

Changing from individual approval to autonomous execution changes when your decisions are made. Review the permissions, risk tolerance, and operating arrangement before making that change. Also consider any positions already open and ask us to explain the actual transition procedure. Moving in the opposite direction deserves the same care: a preference for more involvement should be reflected in the arrangement, rather than assumed from what you last said in a chat.

Separate stopping activity from closing exposure

Stopping new trading, closing positions already open, disconnecting an assistant, and revoking permissions can have different effects. Ask us to explain the procedure for the arrangement you use before you need it urgently. Keep a record of open exposure and outstanding billing questions when planning a pause. A stopped interface should not be treated as proof that every financial position is closed or that every previously granted permission has changed.