Verification register Agentic Commerce & Payments
Current reading
The readiness gap, in one scan
AI-assisted assembly · derived results
- Claimed
- 58
- Reported
- 54
- Verified
- 47
- Gap
- +11
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed minus verified
Evidence strength Growing
Decision
What the current evidence supports
Human editorial judgment · 2026-06-28
Proceed with caution
- Why
- DAP's provenance + user-binding + permission-scope + code-integrity model is closely aligned with our trust-authority credential architecture and its AP2 integration fits our protocol stack, but the lack of published pilots/availability dates and the unsettled standards landscape make a vendor commitment premature.
- Next
- Read Trulioo's KYA white paper and map DAP's lifecycle checkpoints (developer/provenance identity, user binding, permission scope, behavior telemetry, continuous risk scoring, code integrity) against our 3-layer Trust Graph (Identity DIDs/credentials in trust-authority, Interactions in unified Supabase, per-platform routing); assess whether DAP is a credential format we could issue/consume rather than a vendor lock-in.
Constraints
Blockers
No named blocker is present in the current public projection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 7
- Tier 1
- 0
- Tier 2
- 5
- Tier 3
- 2
- Supports
- 4
- Contradicts
- 2
- Context
- 1
- Latest observed
- 2026-01-20
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Initial public reading
This is the initial public reading. No earlier readiness change is recorded.