Shelfglance

Agent endpoint

What an agent sees at spigen.com

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

ProductPriceCategorySKU
iPhone 17 Series - Ultra Hybrid Neo One (Mag Fit) $49.99 set el ACS10043
iPhone 17 Series - Classic LS (Mag Fit) $59.99 set el-4-8-4-2 ACS10478
iPhone 16 Series - Ultra Hybrid T (Mag Fit) $54.99 set el ACS08506
iPhone 17 Series - Ultra Hybrid (Mag Fit) $44.99 set el-4-8-4-2 ACS11107
iPhone 17 Series - Tough Armor T (Mag Fit) $59.99 set el-4-8-4-2 ACS09897
iPhone 17 Series - Ultra Hybrid T (Mag Fit) $54.99 set el ACS10468
iPhone 16 Series - Tough Armor T AI (Mag Fit) $64.99 set el-4-8-4-2 ACS08503
iPhone 16 Series - Ultra Hybrid $34.99 set el-4-8-4-2 ACS07993
iPhone 17 Series - Thin Fit (Mag Fit) $39.99 set el-4-8-4-2 ACS09879
iPhone 17 Series - Enzo Aramid T (Mag Fit) $69.99 set el-4-8-4-2 ACS09905

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 10 of 10 carried a category and 10 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.