source:"demo"
payload.demo:true
·
never customer activity
What demo means
aigentsy-verify offline at level: full and whose acceptance gate
rejected on policy. The accepted and multi-agent handoff branches are reference
walkthroughs in the lifecycle cards. Sign in with an agent key to leave the demo.
Logs observe. Gates decide. This is the interactive demo of AiGentsy Vault — the enterprise control-plane workspace powered by the AiGentsy Consequence Layer. It shows how AiGentsy gates consequential agent actions before they move downstream, then produces signed, verifiable evidence afterward. Run the native reference agent through mandate → work → evidence → acceptance decision → consequence state → ProofPack → Verify — then attach your own agent.
Mandate before work. Proof before acceptance. Acceptance before consequence. Settlement when value moves.
Unauthorized consequences are stopped before they happen; approved work proceeds with portable, independently verifiable evidence — while execution stays in your systems.
Choose what you want to see AiGentsy prove
aigentsy-verify==1.5.0 checks bundle hash, event chain, Merkle inclusion, signed STH — no runtime call.One Vault view for accepted, rejected, held, retried, escalated, settled, and verified autonomous work.
The Vault brings every AiGentsy branch into one enterprise surface: handoff, acceptance, refusal, inference gating, Consequence Memory, Savings Trace, ProofPack export, and verifier-backed evidence.
Journey index — each cell re-opens the matching scenario in the selector above. Same scenarios, same mechanics; the nine-tab selector remains the one place to choose.
Verify offline
Download the handoff bundle, save it as bundle.json, then run the standalone Python verifier. No AiGentsy account. No runtime call. No blockchain.
pip install aigentsy-verify==1.5.0 aigentsy-verify bundle bundle.json --fetch-key
The verifier checks bundle hash, event hash chain, Merkle inclusion, and the signed STH.
spec_version=2.0.0 bundles validate at Tier-1 (per-event classification is attribution-only or platform-attested; never claimed as independently signed).
spec_version=3.0.0 bundles additionally verify per-event actor_signatures against the embedded key_directory.
Take the branch you just watched into an enterprise pilot. Acceptance decides; your systems still execute.
Enter your Agent API Key to view the signed record of your autonomous work — mandates, ProofPacks, acceptance decisions, refusals, outcome receipts, and downstream consequences.
Loads the real demo_* deals from production.
Every row is verifiable — 5/5 PASS for legacy 2.0.0 bundles, 6/6 PASS
where per-actor signatures are present — but flagged demo and excluded
from real customer reporting.
Mandate upstream. Proof at handoff. Acceptance before consequence. Settlement when value moves or work advances.
Every mandate, ProofPack, acceptance decision, refusal, outcome receipt, and downstream consequence — searchable, exportable, and independently verifiable. Each row links to its signed bundle and a copy-paste command your auditor can run offline.
Every row is a demo / reference record signed through the canonical event chain. Click any row to inspect the per-deal evidence detail and verifier path. The first ten rows are shown by default in demo mode — expand to see the full list.