Definition
An agent mandate is a digitally signed record of what a person has authorized an AI agent to do, such as which item to buy and at what price. In Google's AP2 protocol, mandates are described as tamper-proof, cryptographically signed contracts that serve as verifiable proof of the user's instructions.
Why it matters
When an AI agent places an order, you need to know the buyer really asked for it. A mandate is that proof. It shows what the person approved, so a disputed order can be checked against a signed record instead of an argument.
For a store owner, a mandate also gives you something to apply rules to. You can approve orders that match the mandate, decline ones that don't, or hold unusual ones for a person to review.
How it works
AP2 describes two kinds. An intent mandate is signed up front. In Google's words it sets the "rules of engagement", such as price limits and timing, and lets the agent build a cart later once those conditions are met. A cart mandate is signed when the person approves a specific cart. It creates an unchangeable record of the exact items and price.
The AP2 site also describes the same idea in an open stage, where constraints are set before a cart exists, and a closed stage, where a final checkout is authorized. Terminology is still evolving, so check the current spec before building on it.
Example
A shopper tells an agent: "Buy these running shoes if the price drops below $90." That instruction is signed as an intent mandate. When a store lists them at $85, the agent builds a cart and the order arrives carrying the mandate. Your rules can check the price against the limit before approving. This is one part of agentic commerce.
Sources
- Google Cloud: Announcing Agent Payments Protocol (AP2) · checked 15 Nov 2026
- AP2 Protocol · checked 15 Nov 2026