UCP Product Catalog API: How to Expose Your Inventory to AI Agents

The product catalog is the foundation of agent commerce. An agent cannot purchase what it cannot accurately understand. Most existing product data — optimized for human browsing through search terms, lifestyle photography, and curated descriptions — is poorly structured for agent consumption. UCP’s product catalog API defines a standard schema that makes merchant inventory legible to any AI agent, regardless of the underlying commerce platform.

Why Human-Optimized Product Data Fails Agents

Human shoppers interpret ambiguous product descriptions, infer specifications from context, and use images to fill gaps in textual information. Agents do not. When a product description says large in the title and does not specify dimensions in structured fields, a human might look at the image and make an informed guess. An agent will either fail to match the item to the buyer’s requirements or purchase the wrong size. Structured, machine-readable product data is not a nice-to-have for agentic commerce — it is the minimum viable catalog.

UCP Catalog Schema: Core Fields

The UCP catalog schema requires specific fields that most commerce platforms support but rarely enforce: a canonical product identifier (not a variant SKU, but a root product ID), complete structured attributes (dimensions, weight, material, compatibility), a machine-readable condition field (new, refurbished, open box), availability status with restock date if applicable, and pricing structured as base price plus a complete fee schedule including shipping estimates by zone. Every field has a type and a validation rule. Ambiguous data is rejected at catalog ingestion, not at purchase time.

Variant Architecture for Agent Commerce

Product variants — size, color, configuration — require explicit parent-child architecture in the UCP catalog. Each variant must carry the full attribute set that distinguishes it from sibling variants. An agent selecting a size medium blue widget must be able to identify that specific variant unambiguously, add only that variant to the cart, and confirm that the variant is available at the stated price before completing the purchase.

Catalog Freshness and TTL

Stale product data causes agent errors. A price or availability status that was accurate when the agent cached the catalog and is no longer accurate when the purchase is attempted creates transaction failures that are frustrating for the human behind the agent and damaging to the merchant’s agent commerce performance metrics. UCP catalog records include a mandatory TTL (time to live) field specifying how long the record can be cached before requiring a fresh fetch.

Frequently Asked Questions

Does my Shopify or WooCommerce store automatically support the UCP catalog schema?

Not automatically. UCP provides platform-specific plugins for Shopify, WooCommerce, Magento, and others that map the platform’s native product data to the UCP catalog schema. The plugin handles the translation; merchants still need to ensure their native product data is complete and structured.

Frequently Asked Questions