Docs

Documentation

Concepts and short guides for the Agent Action Capsule — the open profile for verifiable records of what an AI agent did, and the transparency layer it builds on.

Concepts

What is an Agent Action Capsule?
A signed, tamper-evident record of an agent action — and the three properties that make it verifiable.
Statement vs transparency layer
What happened vs where it is recorded — and why the statement is structure-independent.
What is a Transparency Service?
Register, receipt, anchor — and the boundary between a transparency service and a verifier.
Verifiable Data Structures
RFC9162_SHA256 (vds=1) vs CCF ccf.v1 (vds=2), and what stays constant across them.
How verification works
Two independent checks: signature, then inclusion proof — both from the bytes, offline.

Guides

Quickstart
Seal your first capsule with one emit() call, anchor it, and verify. Copy-paste-runnable.
Verify a capsule
Verify in the browser, on the command line, or as a library — same checks everywhere.
A2A + AP2 example
A2A callee seals a neutral capsule on every AP2 payment. CartMandate is the “may” — the capsule is the “did.” Runnable, anchored, verifiable.

Live & interactive

Explore a capsule
Interactive: click each field, edit what goes into a digest, tamper one and watch the seal break, then verify a bundle as a skeptical auditor.
The public log, live
Watch the transparency log in real time — total entries, latest checkpoint, operating-since, and the most recent records. Public, verifiable, nothing fabricated.

Reference

Glossary
SCITT, COSE_Sign1, Signed Statement, Receipt, VDS, STH, inclusion & consistency proofs.
Building on it? Implementation, tutorials, and adapter guides live in the canonical capsule-emit docs: capsule-emit/docs ↗. These pages cover the standard-level concepts; the repo docs cover hands-on usage.
Status. The Agent Action Capsule profile is an individual IETF Internet-Draft (draft-mih-scitt-agent-action-capsule) — submitted for discussion, not adopted by a working group, and not a standard. It builds on the IETF SCITT and COSE drafts, which are themselves still in progress and not yet published as RFCs. RFC 9162 (Certificate Transparency 2.0) is a published RFC. Tracking the standard: this profile is built to track SCITT and COSE as they finalize — as those drafts advance and are published as RFCs, the profile and its reference implementations will be updated to conform to the final versions, and any breaking changes will be versioned and documented.