From ap2-agentic-payments
Implements AP2 payment protocol as A2A extension in multi-agent systems: mandates DataParts in messages, Agent Cards for capabilities, payment task flows, and inter-agent communication.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ap2-agentic-paymentsThis skill is limited to using the following tools:
**Fetch live docs**:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Fetch live docs:
https://ap2-protocol.org/specification/ for the A2A extension specificationhttps://ap2-protocol.org/topics/ap2-a2a-and-mcp/ for protocol integration detailssite:github.com google-agentic-commerce AP2 a2a extension for reference implementationsite:github.com google-agentic-commerce AP2 samples a2a for A2A-based samplesAP2 is designed as a direct extension of the A2A protocol. It adds payment-specific capabilities to A2A's general-purpose agent-to-agent communication:
As the documentation states: "A2A is required to standardize intra-agent communication — as soon as you have more than one agent you need A2A." AP2 adds payment standardization on top.
AP2 agents declare payment support in their Agent Card:
{
"name": "MerchantAgent",
"capabilities": {
"extensions": [
{
"description": "AP2 Payment Extension",
"required": true,
"uri": "https://ap2-protocol.org/extension/v1"
}
]
},
"skills": [
{
"id": "checkout",
"name": "Cart and Payment",
"description": "Handles product search and cart creation",
"tags": ["ap2", "payment", "commerce"]
}
],
"security": [...],
"securitySchemes": {...}
}
AP2 mandates are transmitted as DataParts within A2A messages:
Each phase of the AP2 flow maps to A2A tasks:
A2A messages carrying AP2 mandates include:
{
"role": "user",
"parts": [
{
"type": "text",
"text": "I want to buy a coffee maker"
},
{
"type": "data",
"data": {
"intent_mandate": { ... }
}
}
]
}
┌─────────────────────────────┐
│ AP2 (Mandates, VDCs, Signing)│
├─────────────────────────────┤
│ A2A (Tasks, Messages, Parts) │
├─────────────────────────────┤
│ HTTP / JSON-RPC 2.0 │
└─────────────────────────────┘
Shopping Agents discover AP2-capable merchants by:
.well-known/agent-card.json or registries)capabilities.extensions[]The reference samples include a watch.log that captures:
This is valuable for debugging the A2A ↔ AP2 integration.
Fetch the specification for exact A2A extension schema, DataPart structures for mandates, and Agent Card AP2 capability declaration before implementing.