Skip to content
Agent Protocol Stack

Anumati / ACAP

Anumati (Sanskrit for consent, formal permission) defines the ACAP specification: Agent Consent and Adherence Protocol.

The Gap

Section titled “The Gap”

The A2A AgentCard communicates what an agent can do. It has no mechanism for communicating what calling agents are permitted to do under the callee’s terms of service. Auth policy (OAuth scopes, RBAC) governs who may call which endpoint. Usage policy governs how and under what conditions a permitted action may be taken.

Under UETA §14, the human principal is legally bound by whatever terms their agent accepts, without necessarily being aware. ACAP closes this gap.

Three Primitives

Section titled “Three Primitives”
PrimitiveWhat it records
PolicyDocumentThe callee’s versioned, machine-readable terms of service
ConsentRecordThe calling agent’s parsed understanding and acceptance decision
AdherenceEventThe calling agent’s per-action policy evaluation with reasoning

Together they shift consent from proof of acceptance (“I clicked agree”) to proof of adherence (“I evaluated §3.4.2 before acting and here is my reasoning”).

Formal Verification

Section titled “Formal Verification”

Seven safety properties and two liveness properties model-checked under TLC. The TLA+ specification covers chain integrity, consent-before-action, version-gated re-acceptance, and the no-disputed-permit invariant.

Section titled “Links”