Hedera Says AI Agents Can Create Transactions for Signing

Hedera says its AI agents can now create transactions for wallet signing, a workflow the network describes as keeping users in control while automating the setup work, though the claim rests on Hedera's own statement and has not been independently tested. The distributed ledger project made the claim in a post dated September 15, 2026, identifying a Hedera Network MCP plus Wallet Connector as live in Claude Code, according to Hedera's post on X. In its telling, AI agents assemble Hedera transactions while the user's wallet signs them, so the person retains final control over what gets submitted. For related coverage, see OKX Says Senate Will Vote on Advancing CLARITY Act. The framing is narrow on purpose. Hedera is describing agents that draft transactions for a human-held wallet to approve, not agents that move funds on their own. What supported wallets, network scope, and rollout timing look like in practice are not established by the announcement itself. For related coverage, see Anchorage Announces Native Swaps in Porto on Robinhood Chain. KEY TAKEAWAY Hedera reports that AI agents can create Hedera transactions. Those transactions are intended for signing by the user's own wallet. Supported wallets and rollout details are not established by the supplied context. Transaction creation and wallet signing are distinct steps The wording matters. Creating a transaction means an agent has assembled the instructions; it does not by itself mean the transaction has been signed, submitted, or confirmed on the network. Hedera's phrasing, transactions created "for wallet signing," keeps those two steps separate. That separation is visible in Hedera's own tooling. The official Hedera Agent Kit repository documents a RETURN_BYTES mode that hands serialized unsigned transaction bytes back to the caller for external signing, which lines up with the wallet-signing description in the announcement. The same documentation also describes a separate AUTONOMOUS mode that signs and broadcasts using an operator key configured on the client. Those are distinct configurations, so the wallet-signing claim should not be read as a rule that every Hedera agent setup routes through a user's wallet. The Agent Kit package list also includes a Model Context Protocol server toolkit, the component category the new integration falls under. On its face, the headline does not establish that agents can execute autonomously or that they gain access to wallet keys. It also does not, on its own, prove that every transaction requires a manual tap of approval; the exact custody and permission model for this specific integration is not spelled out in the announcement. Readers weighing the feature can compare it against Hedera's earlier Network MCP and Wallet Connector launch coverage for how the pieces fit together. What remains unconfirmed about Hedera's AI agent capability Several practical details are absent from the material at hand.