What Verifiable Intent enables
Verifiable Intent shows how a user's approval leads to an agent's action. A cryptographic delegation chain connects identity, instructions and execution. It can record limits on amounts, permitted merchants and budgets for systems to verify.
Connections with other protocols
- The documentation shows how delegation evidence can map to AP2, ACP and UCP.
- In a purchase, the commerce protocol supplies transaction data. Verifiable Intent connects the action with the scope approved by the user.
Versions and licence
- Published version
- 0.1.0 (changelog) ·
- Working draft
- v0.1
Mastercard's public announcement is dated 5 March 2026, which differs from the changelog date.
- Licence / terms
- Apache-2.0
Licence and terms ↗
An example flow
- A user allows their agent to shop with selected merchants within a budget.
- The approval becomes a signed part of the delegation chain.
- The agent binds its specific action to that approval.
- The recipient verifies the chain and checks the action against the recorded limits.
SDKs and examples
These libraries and examples help you get started. Each entry lists the language, package and supported version.
From the protocol projectPython
Verifiable Intent Python
Includes: Reference SDK
Package / module: verifiable-intent
Version & compatibility: Package metadata 0.1.0, Alpha; Python ≥3.10
Practical integration
- The specification uses SD-JWT and cryptographically binds the stages of delegation together.
- Amount, payment recipient and merchant are machine verifiable constraints. Descriptive product attributes provide additional context.