Build order
Simulation, then limited payments on mainnet with small amounts, then trials with users. Renaming a tool does not make a different product. The one thing worth testing here is whether many agents' costs in one dashboard are easier to run.
Budget simulation
Open nowLimited payments on mainnet
Contract tested, not deployedTrials with users
Not started
Where things stand
| Part | State on 5 Nov 2026 |
|---|---|
| Budget simulator | Works. No wallet. Share a link or save locally. |
| Spend desk contract | Written and tested. Not deployed yet. Mainnet comes first. |
| Fleet dashboard, requests, freeze, allowance controls | Built and tested on a local chain. Waits for the desk to be deployed. |
| Cost reports with CSV export | Built and tested on a local chain. Reads desk events. |
| TypeScript client and sample agent | Works on a local chain. |
| Test network option | Optional, in the app. The network answered on 5 Nov 2026. The desk and a valueless practice token have not been deployed there. |
Planned, not built
| Part | What it would be |
|---|---|
| Advanced cost reports Planned | Trends, per-team rollups and alerts. Basic reports exist; these do not. |
| Multi-agent premium Planned | Paid management for larger fleets, if trials show a need for it. |
| $BURZO for premium Planned | A candidate way to pay for the two rows above. The need for a token is unproven: a useful product comes first, and premium access alone does not explain why a token would be needed. |
Not part of this project
Cards, bank rails, fiat, invested balances and partner integrations. If one of those appears here later, it will have been built first.