How it works and what it can't see
Draft wording (E2 local build).
What is checked
| Section | What we read | When it becomes a finding |
|---|---|---|
| Resources | SUI, WAL and stablecoin balances; up to 10 pages of the address's recent transactions (7 days when that fits) to measure the gas it actually paid and its recurring flows. One-off transfers are not counted as consumption. | SUI runway under 3 days: critical; under 14 days: warning. WAL under 14 days: warning. If repeated top-ups from one address cover the consumption, the finding stays a warning and says the agent depends on them. |
| Transactions | The transactions the address sent in the same window, with the failure cause. Move aborts are named from the chain (clever errors) or from a table of the 10 packages that fail most on mainnet. | 5 failures in a row, or ≥ 50% of recent transactions failing (at least 4): critical. ≥ 10%: warning. |
| Storage | Walrus Blob and Storage objects owned by the address; the current Walrus epoch and storage price. | Certified blobs expiring in under 3 days: critical; under 14 days: warning — with the WAL needed to extend them by one epoch. |
| Network | The newest checkpoint on 4 public endpoints of three operators, and the time from their servers. | The network head more than 30 s behind: warning; more than 5 min: critical. |
How the overall state is decided
Critical if any finding is critical; At Risk if any is a warning; Degraded if consumption or failures are rising without crossing a threshold yet; Unknown if we cannot see the address's resources or transactions, or a check could not be read; Healthy only when everything visible is within its thresholds. A section we cannot see is never shown as green.
What it can't see
- Gas paid by a sponsor: add the sponsor's address.
- Very active agents: an on-demand check reads at most 500 recent transactions; if they cover less than a day, runway and failure rate are not computed.
- Walrus blobs owned by another address or wrapped in other objects: add the owner's address.
- Your agent's own RPC endpoint, its logs, retries and tool errors: these need continuous monitoring or an integration.
- Anything before the window it reads, and anything that happens after the check.
Privacy
Addresses are used only to query public Sui endpoints and to build your report. They are not stored. To count how many distinct agents are checked, we keep a keyed hash of the address set, the date, the result and the number of calls. The written explanation, when enabled, receives the findings with addresses replaced by labels (A1, A2…).
VISIBLE ONLINE · Check an agent · How it works and what it can't see · Addresses are not stored.