Docs
The panel
The panel is where the owner works: every budget with its meter and its switch, the ledger of what the agents paid, and the controls. Here is each screen and what each control signs.
Your panel
The panel belongs to one wallet. Connect it and press Open panel: one transaction creates the panel at an address derived from the wallet, so the same wallet always finds the same panel, on any device.
Each budget is one row of the panel.
| On the row | It shows |
|---|---|
| The label | The name you gave the agent. |
| The meter | What the key has spent of this period’s limit. The stop at its end is the limit. |
| The state | Live, Tripped, Off, Expired or Closed. |
| The switch | The breaker itself. Press it to switch the budget off or on. |
The panel follows the chain as it moves. A payment an agent makes, a trip, a roll at the end of a period: each appears on its row without a reload.
The reserve
Beside Funded, the panel shows its reserve, with Fund reserve and Withdraw. Budgets that draw fill from it; the Budgets page says when.
Switch all off
Switch all off, on the panel, switches off every budget that is on, and your wallet signs them together. Every agent key is revoked and all the money stays where it is.
Team
A panel can have members: wallets the owner adds with the Switch role, the Limits role or both. A member connects its own wallet and finds the panel listed beside any it owns, with only the controls its roles allow. A panel owned by a Squads vault turns each owner control into a proposal, with Approve and Execute. The Team page has who can press what.
New budget
New budget opens a form with a label, an agent key, a limit, a period, an optional expiry and the first funding, from your wallet or from the reserve. The Quickstart goes through each field.
The agent key is either generated in the browser or pasted as a public key. A generated key is shown once on the confirmation screen, with the budget’s address, ready to copy into the agent’s environment. Agent keys has both ways.
A budget’s page
Press a row to open the budget. The page holds everything about one agent.
| Part | It shows |
|---|---|
| The head | The label, the state, the breaker, and the meter with what was spent of the limit. |
| The figures | What remains this period, what the budget account holds in USDC, when the period ends, and the expiry if there is one. |
| The periods | One column for each closed period, drawn against the limit, so a week of spending reads at a glance. |
| The ledger | Every payment the key made: the amount, the service it went to, the time, and the transaction. |
| The agent key | The public key now approved, with a copy button. |
The controls
Each control opens a review that says what will change, then asks the wallet for one signature. Nothing changes until that transaction lands.
| Control | What you enter | What it signs |
|---|---|---|
| Switch off | Nothing. | The key is revoked from the next slot. |
| Switch on | Nothing. | The key is approved for what remained. |
| Reset | Nothing. | The full limit is granted now. The period keeps its end. |
| Change | A limit, a period, an expiry. | The new terms, and an allowance worked out from them. |
| Fund | An amount. | The amount moves from your wallet to the budget account, less the fee. The review shows all three figures. |
| Withdraw | An amount. | The amount moves back to your wallet. |
| Draw from the reserve | On or off. | On, the budget fills from the reserve each time its limit is approved. Off, it keeps its balance. |
| Rotate key | A new key, generated or pasted. | The new key is approved and the old one pays nothing. |
| Close budget | Nothing. | The whole balance and the rent come back to your wallet. |
What each control leaves approved to the key is on the Budgets page.
Activity
Activity is one ledger for the whole panel: every payment from every budget, newest first, each with its budget, its service and its transaction. New payments arrive at the top as they settle.
What the wallet signs
Every transaction the panel hands the wallet is built for that wallet alone, with the owner as its only signer. The agent key is named in them as a public key and never signs anything the panel builds.
The same builds are open over HTTP, so anything the panel does can be done from a script: see Owner transactions on the API page. The panel’s rows come from the same reads, and its live updates from the stream at /v1/panels/:panel/events.