Tools / Register

Make it publicly provable.

A seal alone proves who and what. Registering anchors it in a public, append-only Merkle log — proving when, and that no one can quietly remove or alter it later.

What it means.

When you register a sealed bundle, its hash gets appended to a Merkle log — a public, ever-growing tree where adding any leaf changes the root. The log publishes signed root hashes regularly, so anyone can pin a snapshot in time. To prove a bundle was registered, you walk a small list of sibling hashes from leaf to root.

What gets registered.

Sealed bundles

Attestations

AI agent declarations

Public commitments

Audit packs

How to do it on VLI.

CLI

clearkey upload bundle.json

MCP

vli_seal_event(...)
vli_registry_query(...)

From mcp-server-vli

API

POST /registry-api/log/{logId}/entries
Content-Type: application/json
{ "bundle": {...} }

Under the hood.

</> Inclusion proof

{
  "leafIndex": 4127,
  "treeSize":  81234,
  "leafHash":  "sha256:...",
  "auditPath": ["sha256:...", "sha256:...", "sha256:..."],
  "signedTreeHead": {
    "rootHash":  "sha256:...",
    "treeSize":  81234,
    "timestamp": "2026-04-27T18:00:00Z",
    "signature": "..."
  }
}

See the live registry.

Try it with a sample.

Download a registered SOC 2 evidence bundle, run clearkey verify locally, and walk its Merkle proof in the explorer. Useful for auditor onboarding.

Download sample bundle →