Use cases
One primitive — a typed, revocable, condition-gated allowance — with a huge surface area. A tour of what people build on Sup, end-to-end. Each is who sets what, and what then happens on its own.
#🤖 An AI trading bot you can actually trust
Set: grant an agent 50 SUI/day on Cetus only, no other coin, no other protocol. Happens: the bot trades continuously inside the cap; its key can never exceed it or touch anything outside its sandbox. Kill it in one transaction. The seed phrase never moves. → Sup Agent · Delegation.
#💬 Talk-to-trade (the AI CFO)
Set: nothing — just chat. Happens: "walk me through SUI on the daily and 4h, then open that long on Bluefin" → the agent researches, draws the structure, and drafts the trade; you tap to sign. Research and execution in one place, keyless. → Trading & perps.
#🔁 Subscriptions & DCA without re-signing
Set: approve a service to pull 5 USDC/month (or buy 10 USDC of SUI every Friday). Happens: the service/keeper pulls exactly that on schedule, bounded by a typed allowance — pause or cancel from your wallet anytime. No unlimited merchant approval, no monthly signing.
#👨👩👧 Family & team wallets
Set: each member is a delegate with their own budget — kid gets $50/week, partner unlimited on groceries only. Happens: one pool, many spenders, one shared ledger — every spend is an on-chain event. Caps and categories are caveat rules. → Build a rule.
#🏛 DAO / treasury operations
Set: sub-delegate attenuated budgets down a hierarchy (a department lead carves child caps ≤ their own), plus a recipient allowlist and a quorum caveat over a threshold. Happens: contributors pay vendors autonomously, but only approved addresses, only within budget, and big spends need a co-sign — all on-chain, all revocable at the root.
#🔐 Conditional, proof-gated spending
Set: attach a rule that only stamps a spend when a condition is provably true — a ZK proof verifies, an oracle price sits in a band, a timelock elapses, or an escrow job is marked delivered. Happens: the funds are simply unspendable until the condition holds, then release automatically within the cap — no key, no human in the loop. Because any rule can gate on any on-chain fact, "pay only when X is proven" is just a rule you write or pick from the marketplace. This is what makes Sup strictly more general than address-based delegation. → Build a rule · The solution.
#🛡 Inheritance / dead-man's switch
Set: name your heirs and a check-in interval. Happens: miss the check-in for N days and a cap-gated payout unlocks for them — no keys, no seed ever shared while you're active. The classic "impossible without giving someone your keys today," made a rule. → /inheritance.
#⚡ In-app swap-and-lend, composed
Set: tap once. Happens: swap on Cetus → deposit to Scallop → log, all in one PTB. If the lend leg fails, the swap reverts with it — never half-done. The building block for one-click DeFi UX. → Build a dApp.
#🤝 Agent-native payments (metered AI / x402)
Set: a small scoped budget to an agent. Happens: it pays for inference, buys a dataset, or settles a metered API/compute bill autonomously, within the cap — the kind of machine-to-machine spending a raw contract could never be trusted with.
#📲 And the everyday: NFC tap-to-pay
Hold two phones together — the wallet beams its address over NFC, the payer scans and sends. Offline-first, no QR. The fancy authorization graph runs on a wallet you'd actually carry. → Launch the app.
The common thread: the owner grants once, the allowance bounds everything, and the user (or a capped key) signs. Everything above is the same pattern, pointed at a different problem. Build your own → Quickstart.
