Loading content
An open protocol for agent-initiated payments, using signed user “mandates” so an agent transacts on someone’s behalf with a verifiable chain of authorization. Rides on A2A. Scope: Agent ↔ Payments. The key architectural concerns are the boundary being bridged, the trust model and interoperability with existing agents and services.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AP2 is an open protocol describing authorization and verifiability for payments initiated by agents.
Google introduced the Agent Payments Protocol in 2025 so human-approved and autonomous purchase orders can be distinguished and payment intent can be cryptographically evidenced.
Think of a digital power of attorney: it defines what an agent may buy and leaves an auditable record of approval.
The task the concept fulfills.
A constraint or prerequisite to consider.
How the concept fits into a larger system.
AP2 provides traceable boundaries for agent payments by separating intent, authorization, and execution. Providers must operate keys, refunds, and disputes securely; a standard does not remove fraud or mistaken purchases.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.