Agent payment protocols, compared

The signature artifact of this reference: a side-by-side matrix of the protocols the registry tracks. Sort by any column; filter to narrow the set.

Legendstrong strongmoderate moderateweak weak not applicableunverified unverified draft

13 of 13 protocols

A2Acommunicationframeworklive2026-09-02
ACPexecutionframeworkstrongmoderateunverified2026-09-23
AMPexecutionhybridyesstrongmoderatelive2026-09-14
AP2authorizationframeworkstrongmoderatelive2026-09-03
AP4Mexecutioncard-railyesmoderatestronglive2026-09-14
ERC-4337custodyprimitivelive2026-09-02
MPPexecutionhybridyesmoderatestrongbeta2026-09-03
P3Pexecutionhybridyesstrongmoderatelive2026-09-03
TAPauthorizationcard-railstrongmoderatelive2026-09-14
UAPauthorizationframeworkstrongweakunverified2026-09-14
UCPcommunicationframeworkstrongmoderateunverified2026-09-23
a402executiononchainnoweakmoderateproposed2026-09-02
x402executiononchainnomoderatestronglive2026-09-03

How to read this

Rows are protocols; columns are comparable attributes. Fit chips show suitability for direct-to-consumer (D2C) and business-to-business (B2B) agent payments. A muted em-dash means the attribute does not apply to that protocol's layer — for example, a communication or authorization layer neither settles value nor has a meaningful "reversible" property. Click a column header to sort. Draft rows are flagged unverified and are excluded from the structured-data claims exposed to machines.