Catalog Lookup Capability
Catalog Lookup Capability
Section titled “Catalog Lookup Capability”- Capability Name:
dev.ucp.shopping.catalog.lookup
Retrieves products or variants by identifier. Use this when you already have identifiers (e.g., from a saved list, deep links, or cart validation).
Operation
Section titled “Operation”| Operation | Description |
|---|---|
| Lookup Catalog | Retrieve products or variants by identifier. |
Supported Identifiers
Section titled “Supported Identifiers”The ids parameter accepts an array of identifiers. Implementations MUST support
lookup by product ID and variant ID. Implementations MAY additionally support
secondary identifiers such as SKU or handle, provided these are also fields on
the returned product object.
Duplicate identifiers in the request MUST be deduplicated. When an identifier matches multiple products (e.g., a SKU shared across variants), implementations return matching products and MAY limit the result set. When multiple identifiers resolve to the same product, it MUST be returned once.
Client Correlation
Section titled “Client Correlation”The response does not guarantee order. Each variant carries an inputs
array identifying which request identifiers resolved to it, and how.
| Field | Type | Description |
|---|---|---|
id | string | The request identifier that resolved to this variant |
match | string | Resolution level: exact or featured |
Multiple request identifiers may resolve to the same variant (e.g., a
product ID and one of its variant IDs). When this occurs, the variant’s
inputs array contains one entry per resolved identifier, each with its
own match type. Variants without an inputs entry MUST NOT appear in
lookup responses.
Batch Size
Section titled “Batch Size”Implementations SHOULD accept at least 10 identifiers per request. Implementations
MAY enforce a maximum batch size and MUST reject requests exceeding their limit
with an appropriate error (HTTP 400 request_too_large for REST, JSON-RPC
-32602 for MCP).
Resolution Behavior
Section titled “Resolution Behavior”match reflects the resolution level of the identifier, not its type:
exact: Identifier resolved directly to this variant (e.g., variant ID, SKU, barcode).featured: Identifier resolved to the parent product; server selected this variant as representative (e.g., product ID, handle).
Transport Bindings
Section titled “Transport Bindings”- REST Binding:
POST /catalog/lookup - MCP Binding:
lookup_catalogtool