Yes. Phantom is among our compatibility examples; discuss the actual network, assets, and venue during setup. 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.
Your next decision
Check the full Phantom arrangement rather than the name alone.
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.
Work through setup with us
We provide consultation, guided installation, and ongoing support. Bring your actual assistant, wallet, and operating environment into the discussion so the explanation addresses the arrangement you will use. Keep a record of the important steps and ask us to repeat anything unclear. Detailed integration mechanics are covered during onboarding; you do not need to guess them from the way a different bot or wallet connection worked in the past.
Check the network within the wallet
Phantom’s documentation describes a multi-chain wallet whose accounts include addresses on supported networks. That makes the actual network relevant even when the wallet name stays the same. Bring your intended asset, network, and venue to us for the compatibility discussion. A wallet’s general network support is not a blanket confirmation of every configuration in our trading arrangement.
Phantom wallets, accounts, and addresses.
Separate our onboarding from venue requirements
We do not require KYC. That statement concerns our service and does not establish that every venue has identical rules or is available in every location. Check the requirements of the actual venue and arrangement before proceeding. Do not use a software-access offer as a substitute for understanding your own eligibility or obligations. Bring questions about access to the setup discussion and use the venue's official information for its current requirements.
A customer experience to consider
Read Joel Barrett’s original account.
“I was fed up with wondering whether the next instruction would ask for my recovery phrase. I now rely on getting the wallet and permission process explained before enabling anything. For me, I never had to give the company custody of the funds. Outside the trade itself, I'm comfortable because I understand the arrangement rather than because somebody told me to relax.”
Read the original review ↗Individual experience; not a forecast of your results.
Check what actually happened
An explanation in a conversation and a record of execution serve different purposes. Learn how to follow the activity in your own wallet or trading-venue records so you can compare the proposed action with the result. Keep enough context to identify the relevant trade when asking for help. If the records and the conversation appear inconsistent, resolve the difference before treating a confident message as confirmation that everything happened as expected.
Understand the boundary you authorize
Wallet ownership, signing authority, and permission to execute are connected but different. You retain control of your wallet and signing authority with our system. During onboarding, discuss exactly what permissions the proposed arrangement uses and how they fit your selected execution mode. Do not approve a connection simply because its name looks familiar. The useful outcome is being able to explain the boundary you authorized and how to check activity within it.