Docs
How Allowance works
How it works
The vault is a Squads v4 multisig you control alone: you are the only member and the config authority, threshold 1, no time lock. The agent is not a member. It holds one spending limit and can only move that coin to the listed addresses, up to the amount per window.
The agent signs its own transactions with its own key. Its one power is the Squads instruction that spends from a limit. Squads checks the amount left in the window, the coin and the destination on chain, and refuses anything else. Allowance has no program of its own and holds no key that can move your funds.
Squads v4 program SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf, immutable (no upgrade authority). The site and its history service only build transactions and index what happened.
The limit
Amount per window. Day, week or month, counted on a fixed grid from the moment you set the limit (not sliding). When a window ends, the whole amount is back at once.
Near a window edge the agent can spend the old window's rest and then a fresh window: up to 2x the amount within minutes.
There is no per-payment cap: one payment can use the whole window.
Changing the limit (amount, period, where it may go, the agent key) removes it and sets a new one in one transaction, because a Squads limit cannot be edited. The new window starts full.
Where it may go
- Pay list. Up to 8 addresses you list. A payment to any other address is refused.
- Top-up. The only destination is the agent's own key. The agent then trades or spends from that key by itself.
- One coin per limit: SOL, or one SPL coin such as USDC. An SPL payee must already have a token account for that coin.
The site never offers an empty list: in Squads that would mean anywhere.
Freeze and withdraw
Freeze = remove the limit (one signature of the owner key); its rent comes back to you. The agent's next spend is refused on chain. There is no separate freeze-only key. Unfreeze sets the limit again with a full window.
Withdraw SOL or coins to your wallet at any time, frozen or not: one transaction that creates, approves and executes a vault transaction signed by you alone. Rotating the agent key replaces the limit; the old key can no longer spend.
What it does not limit
- Swaps are not limited. In top-up mode the limit pays the agent's own key and the agent trades from there by itself; what it buys is out of Allowance's reach. Give it only what you are ready to lose per window.
- No per-payment cap, and no list of coins, venues or apps.
- The window is fixed, not sliding: up to 2x around an edge.
- The owner key controls everything: lose it and you lose the vault; whoever holds it can withdraw.
Cost
Free to create. Squads charges no creation fee. You pay rent (about 0.004 SOL; a limit's share comes back when it is removed) and network fees.
Multisig about 0.002 SOL, each limit about 0.002 SOL; a removed limit's rent comes back. Squads charges no creation fee. The agent pays its own network fees from its key: give it a little SOL for gas (the create form can).
Parameters
| Parameter | Bounds | Set by |
|---|---|---|
| Amount per window | above 0 | owner |
| Period | once, day, week or month (30 days) | owner |
| Coin | SOL or one SPL coin, e.g. USDC | owner |
| Destinations | pay list up to 8, or the agent key (top-up) | owner |
| Agent | one key per limit, not a member | owner |
| Signer for every change | the owner, alone (threshold 1) | constant |
Refusals
A refusal is Squads' own error. Sent as a transaction it lands on chain as a failed one, with a Solscan link, and nothing leaves the vault. The SDK simulates first by default: a refusal it catches costs nothing and is reported to the history service signed by the agent key, labelled as a simulation.
| Code | Meaning |
|---|---|
| 6026 SpendingLimitExceeded | Over what is left in this window |
| 6025 InvalidDestination | The address is not on the list |
| 6004 Unauthorized | The signer is not the agent of this limit |
| 3012 AccountNotInitialized | The limit was removed: the wallet is frozen |
| 6027 DecimalsMismatch | Wrong decimals for the limit's coin |
SDK and MCP
The agent SDK finds the agent's limit, builds the Squads instruction, simulates and sends; on a refusal it throws LimitRefused with the code. Methods: pay(to, amount), topUp(amount), status().
The MCP server exposes status, pay and top_up over stdio for agent frameworks (set ALLOW_MULTISIG). The key stays in that process; a prompt-injected agent can at most spend inside your limit, to your list. A refused call returns REFUSED by the Squads spending limit: <code>.
Trust points
- The limits live in Squads v4 accounts. Squads v4 is an immutable program; Allowance adds no program and no admin power over wallets.
- The history service only indexes. The limit, balances and the frozen state on the dashboard are read from the chain. If the service is down, history is stale; funds are unaffected.
- Rows marked simulated are agent-signed claims about simulations, labelled as such. On-chain rows link to their transactions.
Known risks
- If the agent key leaks, the loss is bounded by the limit per window (up to 2x around an edge), to the listed places. Freeze, then rotate the key.
- In top-up mode everything sent to the agent key is the agent's to lose.
- If the owner key leaks, the vault is gone: it is the only signer.