From ucp-agentic-commerce
Implements UCP Buyer Consent extension for GDPR/CCPA-compliant consent collection in checkout sessions, with boolean fields for analytics, preferences, marketing, and data sales.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ucp-agentic-commerceThis 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://ucp.dev/specification/buyer-consent/ for the canonical Buyer Consent extension specsite:ucp.dev buyer consent for related pages and examplessite:github.com Universal-Commerce-Protocol buyer consent for SDK support and sampleshttps://ucp.dev/specification/overview/ for how extensions integrate with the core specThe Buyer Consent extension adds privacy-compliant consent collection to UCP checkout sessions. It enables merchants to collect and record buyer consent for data processing, marketing, and terms acceptance — satisfying GDPR, CCPA, and other privacy regulations.
Agentic commerce introduces a new challenge: an AI agent acts on behalf of the buyer. Regulations require explicit, informed consent for data processing. This extension standardizes how consent is requested, granted, and recorded across the UCP protocol.
capabilities.extensions[] like all UCP extensionsanalytics — consent for analytics/measurement data collectionpreferences — consent for personalization and preference storagemarketing — consent for marketing communicationssale_of_data — consent for sale/sharing of personal datatrue/false). There is no status enum.All consent fields are optional booleans. The protocol does not define consent as blocking checkout. Merchants may choose to enforce consent requirements in their own business logic, but the UCP spec itself does not mandate that missing consent prevents checkout completion.
| Regulation | Requirement | How Buyer Consent Helps |
|---|---|---|
| GDPR (EU) | Explicit consent for data processing | Structured consent collection with audit trail |
| CCPA (California) | Right to know, right to opt-out | Consent types for data collection and sale |
| LGPD (Brazil) | Legal basis for processing | Consent as legal basis documentation |
| PIPEDA (Canada) | Meaningful consent | Human-readable consent text |
Like all UCP extensions:
buyer_consent in capabilities.extensions[]Fetch the Buyer Consent extension specification for exact field names, consent type enumerations, and schema structure before implementing.