AP2 Intent Mandate → open-mandate constraints

Restructured. "Intent Mandate" was the name for the human-not-present credential in early AP2 releases. The concept — a user authorizing a shape of purchase in advance, which an agent later resolves into a concrete transaction — is intact and central. The structure moved: it is now expressed through the Agent Authorization Framework as an open mandate carrying constraints, which the agent later binds into a closed Checkout Mandate.

Read ap2-agent-authorization first. Treat every concrete field name below as historical illustration, not as the current schema.

Before writing code

Fetch live docs:

1. Fetch https://ap2-protocol.org/ap2/agent_authorization/ for the open/closed mandate model — this is where the intent concept now lives.
2. Fetch https://ap2-protocol.org/ap2/checkout_mandate/ for the open-form constraints (allowed merchants, line items).
3. Fetch https://ap2-protocol.org/glossary/ to confirm current terminology before writing any type name.
4. Web-search site:github.com google-agentic-commerce AP2 code sdk mandate for the current type definitions.

Conceptual Architecture

What the Intent Mandate Is

The Intent Mandate is the VDC for human-not-present transactions. It captures the user's pre-authorized shopping intent with defined constraints, allowing the Shopping Agent to act autonomously within those bounds after the user has left the session.