Live Interactive Demo

Attestify OS — Agent Governance in Action

See how every agent action is evaluated against your policies, attested on-chain, and made tamper-proof in real time.

Illustrative simulation — this walkthrough shows example output shaped like a real evaluation, not a live connection or an on-chain record. For real, on-chain governed activity, see the Trust Ledger or Sentinel.
Zone 1

Agent Action

The agent submits a proposed action with context — wallet, amount, recipient, time, and trust score.

Zone 2

Policy Engine

Sentinel evaluates the action against all active rules: spend limits, KYC, time windows, and counterparty allowlists.

Zone 3

Attestation

A cryptographic receipt is minted — EIP-712 signed, Supabase-anchored, and optionally written to Base L2.

Zone 4

Decision & Proof

The ALLOW / DENY verdict is returned with the full receipt, policy timeline, and on-chain TX hash.

Agent Trust Score 94 / 100
Sentinel evaluation

Agent Profile

agent_treasury_01 · Virtuals Agent
Supervised
Autonomy
42%
Risk
18%
Speed
76%
Transparency
91%

Scenario

Action Config

Action Typetransfer_usdc
Amount100 USDC
Recipient0x4Cf9…2a31
NetworkBase
Initiated10:42 UTC

Active Policies

Spend Limit Guard Max single tx: 10,000 USDC
KYC / Counterparty Check Verified recipients only
Time Window Rule Mon–Fri 08:00–18:00 UTC
Agent Trust Score Minimum score: 70 / 100
On-Chain Attestation Write receipt to Base L2
✓
Request
Received
✓
Policy
Engine
3
Attestation
Minted
4
Chain
Anchor
5
Receipt
Returned
Tasks
1
This session
Uptime
99.9%
Target uptime
Violations
0
This session
Cost
$0.05
Per evaluation
ACTION ALLOWED

Transfer approved · 100 USDC → 0x4Cf9…2a31

All 5 policy checks passed. Receipt minted and anchored to Base L2.

⚡ 38ms · Sentinel v2.4.1
{ "receipt_id": "ATT-7F2A-8D3C-4E9B", "version": "2.0.0", "timestamp": "2026-08-02T10:42:07.381Z", "decision": "ALLOW", "agent": { "id": "agent_treasury_01", "trust_score": 94, "verified": true }, "action": { "type": "transfer_usdc", "amount_usdc": 100, "recipient": "0x4Cf9a8B22e7E3F1D9A2B44c77E3F8d3bC142a31", "network": "base", "initiated_at": "2026-08-02T10:42:07Z" }, "policies": { "spend_limit": "PASS", "kyc_check": "PASS", "time_window": "PASS", "trust_score": "PASS", "counterparty_allowlist": "PASS" }, "attestation": { "chain": "base", "tx_hash": "0x8f3a2b7c4e1d9f0a5b6c3e2d1f8a4b7c9e0d2f3a", "block": 24817453, "confirmed": true }, "eval_ms": 38, "sentinel_version": "2.4.1" }
Simulated evaluation · illustrative example, not live data
✓
Spend Limit Guard
100 USDC ≤ 10,000 USDC limit — passed
+2ms
✓
KYC / Counterparty Check
Recipient 0x4Cf9…2a31 is verified — passed
+9ms
✓
Time Window Rule
10:42 UTC is within Mon–Fri 08:00–18:00 — passed
+14ms
✓
Agent Trust Score
Score 94 ≥ minimum 70 — passed
+21ms
✓
Counterparty Allowlist
Recipient on approved list — passed
+38ms
✓
Spend Limit Guard
supabase · policies · spend_limit_v3
PASS
✓
KYC / Counterparty
supabase · kyc_checks · verified_wallets
PASS
✓
Time Window Rule
supabase · policies · time_windows_v2
PASS
✓
Agent Trust Score
sentinel · trust_engine · score_v4
PASS
✓
Counterparty Allowlist
supabase · policies · counterparty_lists
PASS
Every receipt is signed with EIP-712 structured data, stored in Supabase with row-level security, and optionally anchored to Base L2 via a smart contract call. The combination makes receipts cryptographically verifiable, tamper-evident, and auditable by any counterparty.
EIP-712 Signature
0x7f3a2b8c1e4d9f0a5b6c3e2d1f8a4b7c9e0d2f3a4e5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b
Base L2 Transaction
tx_hash: 0x8f3a2b7c4e1d9f0a5b6c3e2d1f8a4b7c9e0d2f3a
block: 24,817,453
network: base mainnet
status: ✓ confirmed
Output Hash
sha256: 0x3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e