agenticweb.wiki

Verifiable Intent (VI) vs Agent Audit Trail (AAT)

They sit at the same step and overlap in purpose; the fields above are the basis for choosing.

Verifiable Intent · Agent Audit Trail

Verifiable Intent VIAgent Audit Trail AAT
Lifecycle step9 Account: Prove what happened; be judged9 Account: Prove what happened; be judged
AnswersAfter an agent completes a purchase on a user's behalf, can the merchant, issuer and consumer all point to the same cryptographic record of what the user actually authorized?Is there a standard, tamper-evident log format any autonomous AI agent can write its actions to, so a regulator, auditor or victim can later reconstruct exactly what it did and why?
Governed byMastercard; contributed to the FIDO Alliance Payments TWG (2026-04-28); built on FIDO Alliance, EMVCo, IETF and W3C primitivesIETF individual Internet-Draft; not adopted by any IETF working group, 'not endorsed by the IETF' and has 'no formal standing' in the IETF process (datatracker's own disclaimer)
Status (issuer's words)Draft (v0.1); open-sourced specification and reference implementationActive Internet-Draft (individual submission), Intended status: Standards Track; not a Working Group document
Version0.1-draft (2026-02-18)draft-sharif-agent-audit-trail-08 (2026-10-13)
Form / transportdocument formatdocument format
Found atnonenone
Implementationprototypenone found
Evidence4 verified3 verified
Primary use caseLet agents buy on behalf of a personAudit what an agent did
Last verified2026-10-23 (current)2026-10-23 (current)
Specificationhttps://verifiableintent.dev/spec/https://datatracker.ietf.org/doc/html/draft-sharif-agent-audit-trail-08

When to use which

Guidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.

Read the full articles

Ask the MCP server to compare any two: the compare-protocols prompt, or get on both ids. Connect.

vi.json · agent-audit-trail.json · Markdown