product · substrate

Built on Microsoft AGT

The Agent Governance Toolkit is the open-source kernel — identity, policy, hash-chained audit log. Wytness is the compliance product on top.

Microsoft released AGT in April 2026, MIT-licensed. It runs inside your agent code: every tool call is policy-checked, allowed or denied, and written to a hash-chained audit log under an Ed25519 agent identity. What it doesn't have: a dashboard, customer-held keys, per-event signing, Evidence Packs, or a hosted service. Microsoft's answer for visualisation is Application Insights — fine for engineers, not for compliance officers.

integration

Two ways in. Both real.

Run AGT with our wrapper, or point AGT's native CloudEvents sink at our ingest with zero Wytness code on your runtime. The dashboard works either way; customer-held keys and Evidence Packs need the wrapper.

install

# Path A — wrapper (recommended). AGT pulled automatically.
pip install wytness-ai
 
# Path B — direct ingest. Install AGT only; no Wytness on your runtime.
pip install agent-governance-toolkit

path a · wrapper

1# Path A — wrapper. Two lines, that's it.
2import wytness_ai
3wytness_ai.init(pii_fields=["customer.email"])
4 
5# AGT runs as normal. Every AuditLog().log() call now flows through
6# the Wytness envelope path — PII tokenised, signed, posted to /ingest.

path b · direct ingest

1# Path B — direct. AGT alone, point its audit sink at our /ingest.
2from agentmesh.governance.audit import AuditLog
3from agent_os_kernel.event_sink import GovernanceEventProcessor
4 
5# Audit stream — AGT's AuditEntry, emitted as CloudEvents 1.0
6audit = AuditLog(secret_key=os.environ["AGT_HMAC_SECRET"])
7 
8# Governance stream — agent_os GovernanceEvents
9processor = GovernanceEventProcessor()
10 
11# Point both at /ingest. AGT batches and POSTs CloudEvents itself.
12WYTNESS_INGEST = "https://api.wytness.ai/ingest"
13audit.add_http_sink(
14    url=WYTNESS_INGEST,
15    headers={"Authorization": f"Bearer {os.environ['WYTNESS_API_KEY']}"},
16    content_type="application/cloudevents-batch+json",
17)
18processor.add_http_sink(url=WYTNESS_INGEST, headers={...})

Capability	Wrapper	Direct
Dashboard, search, Registry views	✓	✓
AGT hash chain ingested and surfaced	✓	✓
Per-event Ed25519 signing (customer-held)	✓	—
Customer-held PII pseudonymisation	✓	—
Bring Your Own Storage · Evidence Packs	✓	—
Code on your runtime	~3 lines	0 (AGT sink only)

No code at all? The Wytness Collector turns Microsoft Foundry and Copilot Studio logs into collected-tier events without touching the agent.

inherited

What you get for free, because AGT does it

✓Ed25519 agent identity and delegation chains
✓SHA-256 hash-chained audit log per agent
✓Sub-millisecond policy evaluation
✓Prompt-injection and tool-poisoning detection
✓OWASP Agentic Top 10 mapping (published by Microsoft)

the honest comparison

What AGT does. What Agent 365 does. What we do.

Capability	AGT + Studioself-host · Studio planned	Agent 365	Why it matters
Per-event signing with customer-held key	Self-build (months)		Your auditor wants non-repudiation, not “trust us.”
Customer-held PII key (zero-knowledge)	Self-build (risky)		Vendor breach can’t leak raw PII because we don’t hold it.
Auditor-ready Evidence Pack PDFs	Self-build PDF tier		Cuts audit prep from weeks to one click.
BYOS (Azure Blob today; AWS S3 on roadmap)	Self-build storage tier		Audit data sits in your tenancy, not your vendor’s database.
Compliance-officer dashboard	Studio is engineer-facing	partial	Your CFO and CISO can self-serve.
Multi-agent fleet visibility across environments	Studio is local-host only	partial	200 agents in production? Studio is single-instance. Wytness aggregates centrally.
Works without Microsoft 365			AWS-anchored buyers aren’t locked out.
Anomaly review queue, HITL routing	Self-build queue	partial	Off-the-shelf incident workflow.