Open numbers
How much Vestiarion is used
Every figure here is read from Vestiarion's production database when the page loads. Arc mainnet and Arc testnet are counted apart, and workspaces that customers opened are counted apart from ours, the ones the team runs to build and test the product.
Read
Arc mainnet
Payments with real money, on Arc mainnet.
No workspace runs on Arc mainnet yet.
Its payments will be counted here, apart from Arc testnet.
Arc testnet
Payments on Arc testnet, where every workspace runs today.
| Figure | Customers | Our workspaces | Total |
|---|---|---|---|
| Workspaces opened | 5 | 8 | 13 |
| Workspaces livenow | 3 | 5 | 8 |
| People in workspacesnow | 4 | 3 | 7 |
| Payments settled | 2 | 65 | 67 |
| USDC paid | 22.00 | 76.40 | 98.40 |
| Payee wallets paid | 2 | 18 | 20 |
| Workspaces that made a first payment | 2 | 4 | 6 |
| Median time from workspace opened to first payment | 5 min | 8 min | 7 min |
| Invoices decided | 3 | 61 | 64 |
| Contractor milestones paid | 0 | 15 | 15 |
| Agent cycles run | 22 | 189 | 211 |
| Decisions made by a model | 25 | 301 | 326 |
| Model departed from the written policy | 1 | 33 | 34 |
| Decisions refused by code | 0 | 12 | 12 |
| USDC in walletsnow | 18.00 | 208.45 | 226.45 |
Outcomes
How the agent's payment decisions turned out: what it carried out itself, what it handed to a person, what people did with its warnings, and whether invoices were paid on time.
| Figure | Customers | Our workspaces | Total |
|---|---|---|---|
| Payment decisions the agent carried out itself | 2 | 53 | 55 |
| Payment decisions it escalated to a person | 1 | 40 | 41 |
| Decided by the agent itself | 67% | 57% | 57% |
| Escalations a person resolved | 0 | 23 | 23 |
| Agent flags a person upheld | — | 0 of 5 | 0 of 5 |
| Invoices paid on time | 2 of 2 | 46 of 50 | 48 of 52 |
| Paid on time with no person involved | 2 of 2 | 33 of 50 | 35 of 52 |
| Duplicate invoices caught | 0 | 0 | 0 |
Settled payments by day
- Customers
- Our workspaces
Show the days as a table
| Day | Customers | Our workspaces | USDC |
|---|---|---|---|
| Sep 30, 2026 | 0 | 9 | 22.40 |
| Oct 1, 2026 | 0 | 10 | 12.25 |
| Oct 2, 2026 | 0 | 17 | 13.85 |
| Oct 3, 2026 | 0 | 19 | 13.30 |
| Oct 4, 2026 | 1 | 4 | 0.90 |
| Oct 5, 2026 | 1 | 6 | 13.70 |
Payments from our own workspaces
The latest payments the team's workspaces settled in this period, so any of them can be checked on Arc testnet. Customers' payments are counted above and never listed here.
- 0.40 USDC0xdff6…ecee(opens in a new tab)
- 1.20 USDC0xeca5…b44c(opens in a new tab)
- 2.00 USDC0x9a11…3225(opens in a new tab)
- 10.00 USDC0x384e…30c5(opens in a new tab)
- 0.50 EURC0x1b63…76df(opens in a new tab)
- 0.10 USDC0x8052…4af0(opens in a new tab)
- 0.10 USDC0xd546…ac0f(opens in a new tab)
- 0.10 USDC0xc508…b155(opens in a new tab)
- 0.10 USDC0x3486…3ab0(opens in a new tab)
- 0.60 USDC0xef98…92ac(opens in a new tab)
- 0.10 USDC0x9c84…fd44(opens in a new tab)
- 0.75 USDC0x9066…b712(opens in a new tab)
- 0.50 USDC0x52b6…51b0(opens in a new tab)
- 0.50 USDC0xd3f4…8d3d(opens in a new tab)
- 1.50 USDC0x4069…25eb(opens in a new tab)
- 0.10 USDC0x662c…e216(opens in a new tab)
- 0.40 USDC0x5bdb…33ad(opens in a new tab)
- 0.50 USDC0x2ca1…92e5(opens in a new tab)
- 0.10 USDC0x49ef…6330(opens in a new tab)
- 2.00 USDC0x365d…9d8b(opens in a new tab)
What counts
- Arc mainnet and Arc testnet are counted apart, and nothing is ever added across them. A workspace belongs to one network, chosen when it goes live and kept from then on; a payment belongs to its workspace's network.
- A payment counts once Circle confirms it on its network. Sandbox workspaces simulate their payments, and those never count.
- A workspace is a customer's when someone outside the Vestiarion team opened it. The team's own workspaces, and any whose creator has since deleted their account, are counted as ours; only workspaces the team opened list their payments.
- A person counts as a customer when they are not on the team and belong to a customer's workspace.
- A contractor milestone counts once a settled payment has paid it.
- A payment decision is the agent's decision on an invoice to pay or a contractor milestone, counted by what happened. Paid, sent or scheduled is carried out by the agent itself; held, flagged or waiting for information is escalated to a person. A payment a model proposed and code refused counts as escalated.
- A flag is the agent saying an invoice should not be paid. A person upholds it by rejecting the invoice and overturns it by paying it; sending it back to the agent counts as neither. A hold or a request for information asks a person to decide, so it is not counted as agreement either way.
- An invoice is paid on time when its payment settles on or before its due day (UTC). No person involved means nobody approved, rejected or returned it; entering the invoice does not count.
- A duplicate is caught when the agent stopped an invoice that repeats one already paid or on its way to being paid, with the same purchase order and amount, and it was never paid since.
- A workspace's first payment is the first one Circle confirms on its network, and the time to it runs from when the workspace was opened. A workspace holding payments from before it was opened counts, but not towards the time. A dash means there is no time to measure in the period.
- USDC in wallets is the USDC in live workspaces' Circle wallets on that network, as last read from the chain.
- Customers' payments appear only as counts and totals, never one by one or as a day's amount.
- Sample data that a workspace loads to try the product never counts.
- Rows marked now are totals at the moment of reading; the others cover the period chosen above.
- A deleted workspace takes its activity out of these figures with it.
- Figures can be up to a minute old.