Skip to the collection

agent-native · Commerce & Payments · Verified 2026-10-13

Agent Payments Protocol (AP2)

Listed on The Agent-Native Index

An open protocol for the emerging Agent Economy

What it does

Agent Payments Protocol (AP2) is an open protocol for verifiable agent payments. Today’s rails assume a human clicked Buy. When an agent pays, merchants cannot answer authorization, authenticity, or accountability from that click model. AP2’s answer is verifiable digital credentials (VDCs) — tamper-evident, cryptographically signed mandates:

Mandates chain into a non-repudiable audit trail for human-present and human-not-present transactions. Samples include human-not-present cards, human-not-present x402, digital payment credentials on Android, and human-present cards.

This is the mandate layer next to catalog x402: x402 is HTTP 402 settlement; AP2 is proof of user intent the merchant and networks can verify. UCP documents AP2 as its secure-payment path.

Freshness: pushed_at on the GitHub repo was 2026-06-17 at verification. Treat the spec and samples as the source of truth; do not infer weekly release cadence.


Agent-facing interfaces

How agents onboard

Interaction pattern: SDK + scenario samples

# Types package (PyPI later; official install is from git): https://github.com/google-agentic-commerce/AP2
uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
Spec / docs https://ap2-protocol.org and repo docs/
Python types uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main
Samples code/samples/python, go, android + run.sh
Web demo client code/web-client/ (Vite + React)
Extensions A2A, UCP; x402 sample

Verification

Last verified 2026-10-13.

Sources: