Wallets
Wallets
Wallets holds the crypto wallets you added by signing with your own browser wallet. MaxSuite never sees your key and never holds your funds. Each wallet is a smart account your key controls on one chain. MaxSuite reads its balances, NFTs and history. You can share a wallet read-only, let agents read it, or let an agent propose swaps, NFT buys or transfers inside limits you set. Each proposal waits for your yes.
In the sidebar under Money → Wallets. Handles money: nothing leaves a wallet without a person saying yes (Agents and approvals).
The Wallets screen
The list shows your wallets, and under Other people's wallets the ones shared with you. With none, the page says No wallets yet.
Add a wallet
- Choose Add wallet.
- Your browser wallet asks you to sign (Waiting for your signature). The signing key becomes the wallet's Owner key.
- Give it a Name. You can Rename it later.
Inside a wallet
Open a wallet for its tabs:
- Holdings: the tokens it holds. Read again refreshes them.
- NFTs: the NFTs it holds.
- History: what it sent and received, with Load more.
- Agents: which agents may read it or act with it, and their limits. Give read access lets an agent read the wallet. To let an agent act, choose what it may do (Swap tokens, Buy NFTs, Transfer to listed recipients) and Each month, at most per token. Change limits adjusts them, and you can take access away. Spent by each agent run shows what each run used. The wallet itself holds the agent's key to these limits on the chain.
- Activity: actions agents proposed and their state. An action waiting for you says Waiting for your yes on its card, and Open this wallet's cards in Approvals takes you there. You can Decline this action with a reason. What Max did with it shows each step.
- Sharing: Share… lets a person see the wallet read-only. Shared with lists them.
Workspace caps
Administrators see Workspace caps: Set a cap for the most each token may move in a month across the workspace, and whether Main networks, which hold real money, may be used. They also see that every wallet exists, without seeing inside it.
Who can do what
| Permission | Lets you |
|---|---|
wallets:read — See your own wallets and those shared with you | Open the page and your wallets. |
wallets:use — Add wallets and let your agents read them | Add wallets and give agents read access. |
wallets:act — Let your agents act with your wallets, within limits you set | Let agents propose swaps, NFT buys and transfers. |
wallets:manage — Set the workspace's spending caps and see that every wallet exists | Set workspace caps and main-network use. |
What happens on its own
| Job | When | What it does |
|---|---|---|
reconcile-actions | Every minute | Moves each action on: from sent to confirmed, to recorded in the books. A reverted action is marked failed. One with no receipt after 30 minutes is marked stuck and its owner is told; it is never resent. An offer that ran out ends, a declined action is closed, and agent access is installed, revoked, suspended for a person who left, or expired. |
Needs
Nothing else switched on. Books records confirmed actions when installed.
What agents can do
Read (read-only): list (the wallets the agent may see), balances, history, action (where one action stands).
Propose (only in wallets it may act with, within its limits): propose_swap, propose_nft_buy, propose_transfer (only to recipients the owner listed).
Send: execute spends money. A person is shown the exact terms (what leaves, the least that arrives, the most the fee can be, the chain and when the offer ends) and it goes only after they say yes. It is sent once.