News Sui
Sui Allowances Spending Caps Add Rate Limits to Agent Keys
Sui introduced native allowances that give users revocable spending caps and rate limits for agent keys. The feature rolled out on testnet in mid-November 2026.
Sui introduced on-chain allowances on November 17, 2026, that let users grant agent keys or other addresses revocable spending permissions with built-in caps and rate limits. The new sui::allowance module creates shared objects that enforce these bounds directly on the funder’s live balance rather than on deposited funds.
Sui Allowances Spending Caps Enforce On-Chain Limits
Every allowance must include at least one amount bound and one time bound. Amount bounds take the form of a lifetime cap or a periodic rate limit, while time bounds cover expiration dates or fixed windows measured in milliseconds from the first spend or anchored to calendar periods such as months or quarters. Unused portions do not roll over between windows, and no single transaction can exceed the active window limit. Timestamps use Unix milliseconds in UTC.
Two variants exist. In the direct model the spender signs transactions itself. In the app-bound model a specific Move module routes the spend and can rotate the spender address without changing the allowance. The funder receives an AllowanceCap object that allows immediate revocation, which deletes the allowance and causes any in-flight transactions to fail. Changing parameters requires revocation followed by issuance of a new allowance.
Documentation updated on the official Sui site on November 17, 2026, and the TypeScript SDK version 2.31 and later include helper functions for creating and monitoring allowances. Checks occur at execution time on the validator, so the system does not rely on off-chain enforcement.
Agent Key Permissions Address Static Credential Risks
Agent keys have become common for automated payments and on-chain actions, yet static keys previously carried unlimited access until manually rotated or expired. The new allowances add native boundaries that reduce exposure when keys are shared with third-party agents or autonomous systems. Rate limits and caps operate on the live address balance, so funds remain under the owner’s control until a spend occurs.

The feature complements earlier testnet tools such as Sui Agent Payments, which handled per-call USDC transfers with receipts, and Agent Pass, introduced at Basecamp 2026, which set broader limits on assets and actions. Complementary simulation tools, including Praxis, can now run risk checks against allowance parameters before deployment. Revocation remains available at any moment through the AllowanceCap, providing a final backstop beyond scheduled expiration dates.
Mainnet activation depends on a protocol feature flag that is already present in the code base. No activation date has been announced. Integrations with external providers, such as Alibaba Cloud agent payments, remain in development on testnet. The design keeps all enforcement on-chain and does not require users to move funds into separate escrow accounts.
Market Impact on Blockchain AI Agent Permissions
Developers building autonomous agents now have a standardized way to grant narrow, time-bound access without exposing full wallet keys. The requirement for both amount and time bounds prevents open-ended permissions that have led to past key-compromise incidents on other chains. Because allowances are revocable objects rather than one-time approvals, owners retain ongoing oversight even after initial issuance.
Ecosystem participants can query allowance status through the updated SDK and monitor spend activity against the defined windows. The approach aligns with broader industry movement toward programmable permissions that support AI-driven agents while maintaining on-chain auditability. Documentation pages include usage examples and an FAQ that clarify edge cases around rate-window calculations and revocation timing.
Frequently asked questions
How do Sui allowances differ from simple approvals?
Allowances enforce both spending caps and rate limits on-chain and remain revocable at any time through an AllowanceCap object. Simple approvals typically lack periodic windows or automatic bounds.
Can an allowance be changed after creation?
No. Parameters are fixed at issuance. To adjust caps or windows the funder must revoke the existing allowance and issue a new one.
Where do the checks occur?
Validation happens at transaction execution time on the Sui network using Unix millisecond timestamps in UTC.
Is mainnet support live?
The feature is available on testnet with SDK support. Mainnet rollout requires enabling a protocol feature flag whose activation date has not been announced.
Comments 1