Sui Agent Pass Caps Losses From Leaked AI Agent Keys at User-Set Limits

Sui Agent Pass at Sui Basecamp

Sui has introduced Sui Agent Pass, a permission framework that keeps an AI agent's actions inside a range the user defines and, if the agent's key leaks, caps the resulting loss at a ceiling the account holder sets. The feature was presented at Sui Basecamp, the ecosystem conference held in Singapore on Wednesday, October 7 and Thursday, October 8. News of the launch circulated through an X post by @EvanWeb3, who demonstrated the capability at the event.

The mechanism addresses a specific failure mode in automated finance. An agent in this setting is software delegated to act for a person: it can execute payments, move funds between accounts, or interact with dapps under standing instructions. To do that, it typically holds credentials that authorize transactions against the connected wallet. If those credentials leak, assets can be moved outside any scope the owner intended. Sui Agent Pass narrows that exposure. Instead of granting an agent unrestricted reach into a wallet, the user draws a boundary and the Sui network enforces it, so the worst case in a leak becomes the preset limit rather than the full balance of the connected account.

Loss containment, not leak prevention, was the explicit focus of the design as presented: the feature does not claim to stop a key from leaking, it bounds what a leaked key can cost. That framing gives delegated authority a middle state it has mostly lacked, somewhere between a key that is fully authorized and one that is revoked. For wallets that act through agents on payments and asset moves, the difference between an unbounded drain and a capped one is the difference between a recoverable incident and a total loss. The presentation did not publish technical specifics such as where the cap is enforced or how quickly it can be adjusted.

Allowances in Sui Developer Docs

Sui's developer documentation describes a related primitive called Allowances. Under that design, a designated user is permitted to spend assets within a defined limit, and the setup carries three controls: a spending cap, a usage period, and the ability to revoke the permission outright. The same documentation describes Agent Payments as drawing on on-chain spending limits, meaning the caps live on the blockchain itself rather than in an off-chain guardrail that a compromised client could bypass. The documentation is the load-bearing primary record here: it is where the spending cap, the usage period and the revocation control are actually specified, and it is the text a developer would rely on when wiring agent permissions.

What the public materials do not settle is how Sui Agent Pass relates to Allowances, or whether the two share an implementation. Allowances are documented as a developer-facing capability; Agent Pass was introduced on stage as its own construct; nothing published so far specifies whether one builds on the other or whether they operate as separate mechanisms. Several enforcement questions are likewise open: whether a cap applies per transaction or across its usage period, whether it resets, and whether it covers every asset in a wallet or only named ones. The shape will be familiar to anyone who has set a card control in traditional finance: a ceiling, a window, and a kill switch, applied to machine spending instead of a plastic card. The analogy holds only so far, since blockchain permissions are enforced by the protocol rather than by a bank's risk system, but the three-part structure, limit, duration, revocation, is the same. Until the technical relationship between Agent Pass and Allowances is published, the safest reading is that Sui has shipped a loss-bounding concept whose exact plumbing has not yet been documented. Base mechanics for the network, for readers new to it, are covered in How to Use Sui, the project's 2026 beginner guide.

The release matters for the risk geometry of agent key leaks: it converts an unlimited drain into a bounded one, which is the variable that decides whether an incident is survivable. How the cap is enforced will determine how much protection it delivers in practice. Sui's developer track has produced other security-adjacent work recently, including Mysten Labs' processing of the first quantum-resistant Sui transaction under protocol version 139. SUI's spot price slipped 6.3% over the last 24 hours, and the Sui technical analysis page tracks the levels traders are watching now. Sui's own materials, for their part, frame Agent Pass strictly as containment: a leaked key costs what the owner preset, and no more.