Payments · security identity · Verifiable Intent Contributors — introduced by Mastercard, co-developed with Google

Verifiable Intent

Verifiable Intent is an open specification for cryptographic agent authorization in commerce, introduced by Mastercard with Google on 5 March 2026. It binds a consumer’s identity, their instructions to an AI agent, and the outcome of the transaction into one tamper-evident record using an SD-JWT delegation chain linking issuer, user and agent, with machine-verifiable constraints such as amount limits, merchant allowlists, budget caps and recurrence rules, and selective disclosure so each party sees only what it needs. It is protocol agnostic, with mappings for AP2, ACP and UCP, and is published under Apache 2.0.

verifiableintent.dev/The standard

Verifiable Intent Contributors — introduced by Mastercard, co-developed with GoogleGoverning body

2026First published

v0.1 draftCurrent version

0providers in the catalog

Also known as VI, Mastercard Verifiable Intent.

Providers that carry Verifiable Intent 0

No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements Verifiable Intent and says so in its APIs.json profile appears here on the next build. Add or correct a listing.

Read from the API Evangelist standards directory, facts verified 2026-09-23. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.