Shelfglance

Agent endpoint

What an agent sees at x10.com

Searching x10.com for x10 the way a shopping agent would returned 10 products. This is what it received.

ProductPriceCategorySKU
X10 WiFi HUB for Android and Apple devices - WM100 $119.99 set na WM100
PMC01 X10 PRO Mini Controller $28.99 not set PMC01
MC10A White Plug-in Mini Controller $25.99 set na MC10A
TM751 Wireless Transceiver $21.99 not set TM751
X10 PAT03/PHR04 Bundle - PRO 16 Channel Transceiver and PRO RF Key Chain Remote $42.99 set na none
PSC01 Powerflash Output Sender Interface $36.99 not set PSC01
XPFM Inline Receiver Module $28.99 not set XPFM
PAT01 16 Channel Transceiver $32.99 not set PAT01
WS13A Decorator Wall Switch $28.99 not set WS13A
PAT03 X10 PRO 16 Channel Transceiver $42.99 not set PAT03

Price, title, description and URL are Shopify’s doing and are filled in for you. Category and SKU are yours, set per product in your admin. Here 3 of 10 carried a category and 9 of 10 carried a SKU.

Read another one

Leave the search term blank and we use the store name. Any Shopify store, not just your own.

What you are looking at

Your store answers AI shopping agents at /api/ucp/mcp, speaking the Universal Commerce Protocol. Shopify switched it on; it is not in your admin and nothing in your theme controls it. We sent it the same search_catalog request an agent would and put the answer in a table. The long version, with what we found across sixty stores, explains why the two columns on the right are the only ones you can change.

This is not a score and nothing here is a fault. If you want the graded version — whether your pages can be read, not just your endpoint — the scan covers that.