Tyler-R-Kendrick/ap2
skills/ai/ap2/SKILL.md
Use when implementing the Agent Payments Protocol (AP2) for secure, compliant AI-driven commerce. Covers intent mandates, cart mandates, payment flows, and merchant integration. USE FOR: agent-driven purchases, secure commerce mandates, user-authorized shopping flows, payment credential verification DO NOT USE FOR: API micropayments (use x402), agent communication (use a2a), tool integration (use mcp)
$ install --global
skillsauthnpx skillsauth add Tyler-R-Kendrick/agent-skills ap2Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 4:48 AM134.4s4 files scanned
SKILL.md
- name:
- ap2
- description:
- |
- USE FOR:
- agent-driven purchases, secure commerce mandates, user-authorized shopping flows, payment credential verification
- DO NOT USE FOR:
- API micropayments (use x402), agent communication (use a2a), tool integration (use mcp)
- license:
- Apache-2.0
- displayName:
- AP2 (Agent Payments Protocol)
- author:
- Tyler-R-Kendrick
- compatibility:
- claude, copilot, cursor
- - title:
- Google A2A Protocol (AP2 Extension)
- url:
- https://github.com/google/A2A
AP2 — Agent Payments Protocol
Overview
AP2 is an open protocol from Google for secure, interoperable AI-driven commerce. It provides a common language for transactions between agents and merchants, preventing a fragmented payments ecosystem. AP2 is designed as an extension for A2A and MCP, adding a secure commerce layer on top of agent communication.
Core Concepts
Intent Mandate
Captures the conditions under which an AI agent can make a purchase on behalf of the user:
- Budget limits (per-transaction, daily, monthly)
- Allowed merchant categories
- Product type restrictions
- Time-based constraints
Cart Mandate
Captures the user's final, explicit authorization for a specific cart:
- Itemized list of products/services
- Total price and currency
- User's cryptographic signature (non-repudiable proof of intent)
- Payment method reference
Payment Flow
User Agent Merchant Payment Provider
│ │ │ │
│── "Buy X" ───►│ │ │
│ │── browse ─────►│ │
│ │◄── product ────│ │
│ │ │ │
│◄── confirm? ──│ │ │
│── approve ───►│ (Cart Mandate signed) │
│ │── purchase ───►│ │
│ │ │── charge ───────►│
│ │ │◄── receipt ──────│
│ │◄── receipt ────│ │
│◄── done ──────│ │ │
Key Design Principles
| Principle | Description | |-----------|-------------| | User control | Users set spending limits and approve purchases via signed mandates | | Verifiable credentials | Cryptographic signatures provide non-repudiable proof of authorization | | Protocol-agnostic payments | Supports pull methods (credit/debit cards) initially, with push methods (bank transfers, wallets) planned | | Compliant by design | Built-in support for regulatory requirements (PCI, PSD2) |
Phased Rollout
| Version | Scope | |---------|-------| | v0.1 | Core architecture, pull payment methods (credit/debit cards) | | Future | Push payments, real-time bank transfers, e-wallets, multi-currency |
AP2 vs x402
| Aspect | AP2 | x402 | |--------|-----|------| | Focus | Full commerce flow (browse → buy → receipt) | Per-request API micropayments | | Payment methods | Cards, bank transfers, wallets | Stablecoins (USDC on Base/Solana) | | Authorization | Intent + Cart Mandates with user signatures | Wallet-signed HTTP headers | | Use case | Agent-driven shopping and purchases | Monetizing APIs and content | | Relationship | Extension for A2A/MCP | Standalone HTTP protocol |
Integration with A2A and MCP
AP2 extends existing protocols:
- A2A: Agent discovers a merchant agent via Agent Card, negotiates purchase via A2A tasks, uses AP2 for the payment step
- MCP: Agent calls a shopping tool via MCP, the tool uses AP2 internally to process the transaction
Best Practices
- Always require user confirmation (Cart Mandate) before processing payments — agents should never make unauthorized purchases.
- Set conservative Intent Mandate limits initially and let users expand them as trust is established.
- Use the verifiable credential model for audit trails — every purchase has a cryptographic proof chain.
- Implement AP2 as a payment layer on top of A2A or MCP rather than as a standalone protocol.
- Handle partial failures gracefully — if payment succeeds but delivery fails, the protocol should support refund flows.
Related Skills
Tyler-R-Kendrick/design-system
tools
VerifiedTrustedCommunity
Use when building or maintaining a design system — the coordinated set of design tokens, component libraries, documentation, and tooling that ensures visual and behavioral consistency across products. USE FOR: design system architecture, choosing token formats vs component frameworks, connecting Figma to code, design-to-development workflows, multi-platform consistency DO NOT USE FOR: specific token authoring (use design-tokens), Figma workflows (use figma), component cataloging (use storybook), token transformation (use style-dictionary), cross-framework components (use mitosis)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/x402
tools
VerifiedTrustedCommunity
Use when implementing the x402 protocol for HTTP-native micropayments. Covers server middleware, client payment flows, facilitator integration, and stablecoin payments for APIs and AI agents. USE FOR: API micropayments, monetizing endpoints, stablecoin HTTP payments, automated agent payments for API access DO NOT USE FOR: full commerce flows with cart/checkout (use ap2), agent communication (use a2a), tool integration (use mcp)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp
tools
VerifiedTrustedCommunity
Use when implementing or integrating with the Model Context Protocol (MCP) for AI tool servers, resources, prompts, and context management. USE FOR: building MCP tool servers, exposing resources to agents, prompt templates, connecting agents to external APIs DO NOT USE FOR: agent-to-agent communication (use a2a), interactive UI rendering (use mcp-apps), agent payments (use x402 or ap2)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp-apps
tools
VerifiedTrustedCommunity
Use when building MCP Apps that serve interactive UI from MCP servers. Covers the ui:// URI scheme, HTML rendering in sandboxed iframes, and bidirectional communication between UI and host. USE FOR: rich UI in agent conversations, interactive dashboards from MCP servers, sandboxed iframe rendering DO NOT USE FOR: basic tool responses without UI (use mcp), agent communication (use a2a), full web applications
10SKILL.mdUpdated Jun 10, 2026