AI agents can already swap tokens, deposit funds, and stake assets on-chain for you. Before letting one take action, the most important thing to understand is: who signed the transaction, and who holds the private key used to sign it?

A private key is the master key to a wallet. Whoever holds it can move the assets inside. A signature uses this key to stamp a transaction, meaning “I agree.” A transaction must be signed before it can be added to the blockchain.

First, let’s define two terms. An agent is an AI that can carry out tasks for you, such as Claude Code or Codex. A skill is a set of instructions written for an agent, sometimes bundled with program files, that tells it what a protocol can do and how to construct transactions. Many protocols on the Sui blockchain have released skills. Their approaches to handling private keys generally fall into three categories.

First, the skill only prepares transactions; you sign them yourself. The README for Haedal, a liquid staking protocol, states that these skills are not wallets and cannot sign transactions on their own. A separate wallet tool that handles signing is needed to complete a transaction; otherwise, the agent can only prepare it for you. Cetus, a decentralized exchange, works the same way: its example produces an unsigned transaction. Turbos, which handles swaps and liquidity, says in its skill file that it will not submit transactions or request signatures without the user's explicit authorization

Second, the agent has its own wallet, and you set a spending limit. WaaP, a wallet service, stores the private key used for signing in a verified secure enclave. The agent's code cannot access the key, and any spending above the daily threshold you set requires your approval. The DeFi Agent in the Sup Wallet app can spend only within authorizations limited to specified uses and amounts. You can revoke an authorization with a single tap, and the app launched with a waitlist and invitation-only access. Sui's official Sui Agent Pass presentation follows the same approach. An official post says: even if the private key is leaked, losses are limited to the cap you chose

Third, hand the entire private key over to a tool. Some community-built MCP servers (a standard interface that lets AI connect to external tools) have installation examples that put the private key directly in the launch command. The tool gets the full private key and has the same permissions as you

The difference is how far the agent can go: the first type stops at preparing a transaction, the second can sign transactions on its own within the limit you set, and the third gets access to the entire wallet

#haedal