Shelfglance

Agent endpoint

What an agent sees at bandedbracelets.com

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

ProductPriceCategorySKU
Banded Blossom - Sea Cliff - 18mm €44.90 set aa-6-3 none
Banded Blossom - Daffodil - 10mm €39.90 set aa-6-3 none
Banded Zoo - Leopard €39.90 set aa-6-3 none
Alicante Sunset 18mm Metallic €44.90 not set none
AZULEJO - Faro - 6mm €34.90 set aa-6 none
Skully - 18mm €44.90 not set none
Skully - 23mm - Classic Finish €54.90 not set none
Hanabi Nights - 10mm - Metallic €39.90 set aa-6-3 none
Banded Blossom - Cherry Blossom - 10mm €39.90 set aa-6-3 none
Waves- Oahu - 6mm €34.90 not set none

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