Shelfglance

Agent endpoint

What an agent sees at seakingbracelets.com

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

ProductPriceCategorySKU
Wörthersee - Deep Diver - Limited Edition €29.99 set aa-6-3 WÖR00115
Wörthersee - Extasy €29.99 set aa-6-3 WÖR00143
Wörthersee - Konfetti €29.99 set aa-6-3 WÖR00171
Wörthersee - Bundle #1 €29.99 set aa-6-3 WÖR0051
Wörthersee Storm Coast €29.99 set aa-6-3 WÖR00301
Wörthersee Wave Sonderedition €29.99 set aa-6-3 WÖR00277
Wörthersee - Vulkan €29.99 set aa-6-3 WÖR00253
Wörthersee Ocean Mist €29.99 set aa-6-3 WÖR00281
Wörthersee - Dark Blue €29.99 set aa-6-3 WÖR00108
Wörthersee - Kalimera €29.99 set aa-6-3 WÖR00167

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.