ucp-agentic-commerce-strategy

What problem does it solve?

UCP agentic commerce briefs and connector designs often drift from the real Universal Commerce Protocol requirements, causing incorrect scope, incorrect data promises, and non-compliant storage decisions.

Core Features & Use Cases

• UCP scope enforcement: Treats UCP as a single protocol family and ensures the agent-surface list matches UCP-covered consumer surfaces (AI Mode, Gemini, Copilot Checkout, Shopify surfaces) rather than unrelated shopping channels.
• Catalog MCP expectations: Prevents review-text workflows by enforcing that Catalog MCP provides aggregate rating data only, not review themes or buyer language.
• No-cache compliance rules: Blocks designs that cache catalog payloads or images, requiring storage of only normalized/derived observations or receipts (hash-based proof) instead of raw upstream data.
• Trust-tier and profile gating: Forces commitment to a concrete UCP agent profile and lowest-tier capability/throughput envelope before publishing.
• Correct merchant authorization model: Routes merchant-authorized data paths through the Modern AI MCP integration rather than ad-hoc credentials.

Quick Start

Use the ucp-agentic-commerce-strategy skill to audit your draft UCP connector and storage plan for compliance with the Shopify/Google constraints.