Ucp Checkout A2a
/install ucp-checkout-a2a
UCP Checkout — A2A Binding
Before writing code
Fetch live spec: Web-search site:ucp.dev specification checkout-a2a and fetch the page for the exact message structure, DataPart keys, and Agent Card format.
Also review Google's A2A protocol spec for the underlying transport: https://google.github.io/A2A/
Conceptual Architecture
What is A2A?
A2A (Agent-to-Agent) is a protocol for autonomous inter-agent communication. UCP's A2A binding lets a Platform agent talk to a Business agent using structured messages rather than REST calls.
How It Works
- Discovery: Business publishes an Agent Card at the URL declared in their
/.well-known/ucpprofile underservices.dev.ucp.shopping.a2a.endpoint. - Communication: Platform sends messages with checkout data in
DataPartobjects. Business agent responds with checkout state inDataPartobjects. - Identification: Platform includes
UCP-Agentheader andX-A2A-Extensionsheader referencing the UCP spec version.
Key Data Part Keys
| Key | Direction | Purpose |
|---|---|---|
a2a.ucp.checkout |
Both | Checkout session data |
a2a.ucp.checkout.payment_data |
Platform → Business | Payment credentials for completion |
a2a.ucp.checkout.risk_signals |
Platform → Business | Optional risk signals |
ap2.merchant_authorization |
Business → Platform | Merchant's JWS detached content signature for AP2 mandate flow |
ap2.checkout_mandate |
Platform → Business | SD-JWT+kb credential proving user-authorized agent checkout |
Message Structure
Messages use A2A's standard format:
messageId: Unique ID (used for idempotency)contextId: Session/conversation IDkind:"message"role:"user"(from platform) or"agent"(from business)parts: Array of TextPart and DataPart objects
Checkout data is carried in DataPart with the appropriate key.
Idempotency
The Business agent uses messageId to detect duplicate requests. Task tracking uses taskId with contextId.
When to Use A2A
- Fully autonomous agent-to-agent commerce (no human in the loop for most steps)
- Multi-agent architectures where commerce is one capability among many
- When you want the Business to maintain its own agent logic (not just expose tools)
Implementation Guidance
Before implementing, fetch the latest sample A2A Business Agent from https://github.com/Universal-Commerce-Protocol/samples (look for the a2a/ directory) to see the reference pattern.
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ucp-checkout-a2a - After installation, invoke the skill by name or use
/ucp-checkout-a2a - Provide required inputs per the skill's parameter spec and get structured output
What is Ucp Checkout A2a?
Implement UCP Checkout over the A2A (Agent-to-Agent) binding — enable autonomous agent-to-agent commerce using Agent Cards and structured message parts. Use... It is an AI Agent Skill for Claude Code / OpenClaw, with 83 downloads so far.
How do I install Ucp Checkout A2a?
Run "/install ucp-checkout-a2a" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Ucp Checkout A2a free?
Yes, Ucp Checkout A2a is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Ucp Checkout A2a support?
Ucp Checkout A2a is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Ucp Checkout A2a?
It is built and maintained by Rohit Bajaj (@ichiorca); the current version is v1.0.0.