From ap2-agentic-payments
Implements AP2 VDC framework with tamper-evident signed credentials for agentic payments. Covers issuance, verification, holder binding, SD-JWT format, and mandate types.
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 VDC framework specificationhttps://ap2-protocol.org/topics/core-concepts/ for VDC conceptual overviewsite:github.com google-agentic-commerce AP2 src/ap2/types mandate for VDC type definitionsap2 protocol verifiable digital credentials VDC for community guidesVerifiable Digital Credentials (VDCs) are tamper-evident, portable, and cryptographically signed digital objects that serve as the trust building blocks for AP2 transactions. They provide:
AP2 VDCs use the SD-JWT with Key Binding (+kb) format, enabling selective disclosure and cryptographic holder binding.
JSON payloads are canonicalized using JCS (RFC 8785) before signing to ensure deterministic serialization.
1. Creation → Mandate generated (by Merchant for Cart, by SA for Intent)
2. Signing → User signs with hardware-backed device key
3. Presentation → Mandate presented to verifying party
4. Verification → Signature and contents validated
5. Usage → Mandate used to authorize payment
6. Archival → Mandate stored for dispute resolution/audit
Every VDC follows a common structure:
The VDC trust model involves:
AP2 VDCs align with W3C standards:
Cart Mandates receive both merchant authorization (a detached JWS JWT) and user signature (hardware-backed device key), forming a dual-authorization model.
To verify a VDC:
Fetch the specification for exact VDC schemas, signature formats, and verification algorithms before implementing.