Docs

Using VISIBLE ONLINE

Two things exist today: the free live check, and the monitoring workspace that is being built. This page says which is which.

The live check

Open the live check, paste the Sui mainnet address your agent sends from (and, if you have them, the addresses that sponsor its gas or own its Walrus blobs, up to 5), and run it. The report gives an overall state, the primary risk, the recommended action, four sections (resources, transactions, storage, network) and what VISIBLE ONLINE could not see. It reads public data only; nothing is signed and the addresses are not stored. How it works lists every threshold.

Monitoring workspaces IN DEVELOPMENT

A workspace keeps your agents and checks them on a schedule, records every run, opens an incident when a finding appears, and alerts you once per incident change — not on every run.

1. Sign in with your email: you receive a one-time link (valid 15 minutes). Your first sign-in creates your workspace.
2. Add an agent: a name and the same addresses as the live check. The free workspace holds up to 3 agents, each checked about once an hour.
3. Add an alert channel: email (to a member of the workspace), Telegram or a signed https webhook.
4. Read the dashboard: the latest state, the history of runs, the open incidents, and what the checks used and cost.

Monitoring is not open to the public yet: it still needs its production database, scheduler and email sender. Until then it runs on development servers, where every simulated run is labelled as simulated.

Incidents

• An incident opens for a critical or warning finding and stays one incident while the finding persists.
• It alerts again only if it becomes more severe, and once more when it resolves.
• It resolves after two checks in a row in which its section is visible and fine. A section VISIBLE ONLINE cannot see never counts as recovered.
• If VISIBLE ONLINE itself cannot run a check three times in a row, a separate incident says so; that is our problem, not your agent's.

Webhooks

Each webhook channel gets its own signing key, shown once. Every request carries x-visible-online-timestamp and x-visible-online-signature: sha256=…, an HMAC-SHA256 of timestamp + "." + body. Reject requests whose timestamp is more than a few minutes old.

Your data

From the workspace settings you can export everything VISIBLE ONLINE holds about the workspace as JSON, or delete the workspace and all of its data.