You can give an AI agent a trading instruction in ordinary language: check your balance, prepare a Bitcoin order, or explain why a transaction failed. Connecting that agent to a wallet gives it a way to act on those instructions.
In the Crypto Hustle demonstration below, Grey Jabesi uses Grok Bot with MetaMask Agent Wallet to prepare a Bitcoin perpetual trade on Hyperliquid. The walkthrough covers creating a dedicated trader, setting a wallet spending limit, giving instructions by voice, and dealing with a missing funding step.
This guide breaks that process into stages you can check before moving to the next one. AI makes the interface more conversational; you still need to understand what you are approving and how much money is at risk.
Watch the demonstration
Watch on YouTube: I Let Grok Bot Trade My Crypto — Here’s What Happened
Useful moments in the video:
- 00:38 — MetaMask Agent Wallet
- 02:20 — Creating the trader agent
- 03:28 — Spending limits and verification
- 05:12 — Requesting a Bitcoin long
- 06:05 — Why the trade needs funding
- 07:37 — Bridge submitted and next steps
What the recording proves: it shows the setup, revised trading instruction, and submission of a bridge transaction. It ends before the Hyperliquid deposit and trade are confirmed. It is a workflow demonstration, with no completed-trade or profit result shown.
Understand the three tools
| Tool | Its role in the workflow |
|---|---|
| Grok Bot | Receives your instructions and uses tools on its computer to carry out tasks. |
| MetaMask Agent Wallet | Provides the agent's wallet interface, including funding, authentication, and applicable wallet policies. |
| Hyperliquid | The venue where the perpetual position is opened and managed. |
Grok Bot is an agent with a computer, rather than simply a chatbot answering market questions. Its ability to take actions makes its permissions worth reviewing before you connect financial tools. See Grok Bot 101.
A Bitcoin perpetual is a derivative position. Opening a BTC long on Hyperliquid does not mean buying Bitcoin into a Bitcoin wallet. You are taking price exposure through a contract, with margin and liquidation considerations.
1. Get Grok Bot ready
Start at the official Grok Bot website and follow its getting-started guide. Install the app, sign in, and check your account's current eligibility. Do not assume an X verification badge alone provides access; use the current plan requirements.
Create a dedicated Bot named Trader and give it a narrow job. A useful starting instruction is:
Help me set up MetaMask Agent Wallet for Hyperliquid. Begin with read-only checks. Show me the wallet address, network, balances, and proposed actions. Do not move funds or place orders until I explicitly approve the specific action. Never ask me to paste a seed phrase or private key into chat.
This is an example instruction for the reader, not a claim that a prompt can enforce every limit. Keep the Bot's actual permissions aligned with the job. Grok Bot supports typed and voice instructions; review the written interpretation of a voice request before approving it. Source: Grok Bot setup documentation.
2. Connect MetaMask Agent Wallet
Give Trader the official MetaMask Agent Wallet quickstart and ask it to follow the installation instructions on its own computer. The CLI must be available in the environment where the agent runs.
For readers handling installation themselves, MetaMask currently specifies Node.js 22.18 or later and these commands:
npm install -g @metamask/agent-wallet@latest
npx skills add MetaMask/agent-skills
Select the metamask-agent-wallet skill when prompted. Then ask Trader to guide you through sign-in and wallet initialization.
For a separate experimental setup, choose a dedicated server wallet instead of importing your main wallet's recovery phrase. Pick one sign-in method and keep using it: MetaMask documents that Google, email passwordless, and MetaMask Mobile QR can load different server-wallet addresses, even when Google and email use the same email address. Confirm the active address before funding. Source: MetaMask quickstart.
Run the diagnostic check before proceeding:
mm doctor
Confirm that authentication and initialization are complete. Resolve any compatibility warnings first. Source: CLI command reference.
3. Set wallet policies and trading instructions separately
For a first experiment, use Guard Mode and a small, dedicated budget. Ask Trader to show the current policy before requesting a change.
Grey uses a $50 daily limit in the demonstration. That is an example from the video, not a recommended budget for every reader.
MetaMask's rolling 24-hour outflow policy and your trading rules do different jobs. Read the outflow policy and trading-mode comparison before funding.
The important boundary: MetaMask explains that its wallet checks apply to the deposit into Hyperliquid. Opening, modifying, and closing perpetual positions on Hyperliquid do not receive those same outflow-limit, allowlist, threat-scanning, or two-factor checks. Guard Mode therefore does not mean every trade requires an email approval. Source: MetaMask's perps safety explanation.
Write separate instructions for maximum collateral, leverage, total exposure, permitted markets, and when the Bot must stop. Treat these as agent instructions unless you have verified a corresponding technical restriction. A spending limit is not a guaranteed maximum trading loss.
4. Fund the correct wallet and network
Ask Trader to display the active address and balances by network. Check the destination independently, then make a small test transfer before sending a larger amount.
In the video, Grey initially funds the wallet with ETH. When he requests a trade, the Bot identifies that additional preparation is necessary: the Hyperliquid account needs suitable collateral.
There are distinct stages to verify:
- Funds arrive in the agent wallet on the intended network.
- Any required swap or bridge completes.
- Collateral is deposited into Hyperliquid and appears in the perpetuals balance.
Do not treat those stages as interchangeable. Ask for the asset, source network, destination network, fees, and expected received amount before approving a route. See MetaMask's swap and bridge guide.
For this Agent Wallet perps workflow, MetaMask documents USDC funding and an Arbitrum default source for deposits. Ask the Bot to verify current support rather than assuming ETH or USDC on any network is immediately usable. Source: perpetuals setup guide.
5. Review the approval request
When a wallet operation requires approval, review the details through the official flow. Browser sign-ins use email approval links; Mobile QR sign-in uses MetaMask Mobile notifications. Source: MetaMask quickstart.
In Grey's example, the verification screen concerns updating the wallet's daily policy. Approving a policy change is not the same as approving a particular trade. Check what permission is changing, which wallet it affects, and the amount involved.
Do not publish login tokens, verification codes, approval links, or private wallet credentials. Keep request identifiers out of public screenshots when they are unnecessary to explain the process.
6. Confirm the Hyperliquid balance before requesting an order
Ask Trader:
Check whether the bridge has completed and whether my Hyperliquid perpetuals collateral has arrived. Show the available balance and any pending requests. Do not retry a transfer or place an order.
Read-only commands useful for verification include:
mm perps balance --venue hyperliquid
mm perps positions --venue hyperliquid
Check the same account in the official Hyperliquid app. Wallet funds, Hyperliquid spot funds, and perpetuals collateral may represent different balances. Follow the Hyperliquid onboarding guide for the venue's funding process.
If a deposit remains pending, investigate its status before submitting another. A submitted transaction is not proof that spendable collateral has arrived.
7. Preview a fully specified trade
Grey first requests a 10× Bitcoin long, then revises the instruction to $10 margin at 5× leverage. That implies approximately $50 of notional exposure before fees and price changes:
$10 margin × 5 leverage = $50 notional exposure.
Those figures explain the demonstration; they are not a suggested trade. A request such as “use $10” is ambiguous unless you say whether it means collateral or total position value.
Before placing an order, ask for a proposal containing:
- Market and direction: for example, BTC perpetual, long.
- Collateral amount, leverage, and resulting notional exposure.
- Margin mode and estimated liquidation information, where available.
- Market or limit order, with a limit price if applicable.
- Fees, slippage limit, and available collateral after entry.
- Stop-loss and take-profit plan, including how to verify the exit orders.
An example preview request:
Prepare a BTC perpetual order proposal on Hyperliquid. Use only the collateral amount and leverage I specify. Explain the resulting exposure, fees, margin mode, and liquidation risk. Show a quote and dry-run result if supported. Do not submit anything until I approve the final details.
MetaMask provides quote and dry-run functionality for reviewing an order without submission. A dry run tests the proposed operation; it does not demonstrate that a strategy will be profitable. Source: trade perpetuals documentation.
8. Verify the fill and exit orders
Once you choose to approve a live trade, verify the result on the venue. Distinguish a submitted order, a resting limit order, a partial fill, and a fully opened position.
Ask Trader to report the filled size, average entry, margin, leverage, and remaining balance. Then check the corresponding position yourself.
MetaMask documents take-profit and stop-loss placement as a separate modification step after opening. Do not assume an entry automatically includes either one. Confirm that any intended exit orders were accepted. Source: MetaMask perps guide.
A stop order also cannot guarantee a particular execution price during fast markets. Continue monitoring collateral, open orders, and funding costs while a position remains open.
Common problems and what to check
| Problem | What to check first |
|---|---|
| The wallet appears empty after signing in | Confirm the sign-in method and active wallet address. |
| The Bot can see ETH but cannot open the perpetual | Verify the required collateral asset and the Hyperliquid funding stage. |
| A bridge is submitted but the trade remains pending | Check destination receipt and the perpetuals balance before retrying. |
| A wallet request needs approval | Read the exact operation; distinguish funding, policy changes, and authentication. |
| The Bot reports success but no position appears | Inspect orders, fills, and positions in the correct Hyperliquid account. |
| The entry exists but protection is missing | Check whether the separate exit-order step completed. |
For command errors, consult the MetaMask CLI reference rather than repeatedly telling the Bot to try again.
Can Grok Bot run a trading strategy automatically?
You can describe a monitoring workflow, such as checking a defined indicator on a schedule and returning a trade proposal. Start with alerts and review whether the Bot interprets the rules consistently before granting execution permission.
A usable strategy needs more than “buy when the market looks bullish.” Specify the data source, market, timeframe, entry condition, sizing, exit condition, maximum exposure, and behavior when information is missing. Also define when the workflow must pause.
The video discusses possible automation, but does not establish a profitable strategy or prove unattended trading reliability. An agent can repeat an error as efficiently as it repeats a useful task. Judge the setup by verifiable actions and records, not confident language.
Official resources
- Grok Bot website and downloads
- Grok Bot getting started
- MetaMask Agent Wallet overview
- MetaMask Agent Wallet quickstart
- MetaMask trading modes
- MetaMask outflow policy
- Swap and bridge tokens
- Trade perpetuals with Agent Wallet
- MetaMask CLI command reference
- Hyperliquid trading app
- Hyperliquid onboarding documentation
Documentation reviewed on October 16, 2026. Interfaces, access requirements, supported routes, and fees can change. Check current availability and eligibility in your jurisdiction before using these services.
This guide is for education, not personalised financial advice. AI agents can make mistakes, and leveraged trading can cause rapid losses. Use only funds you can afford to lose.
