Shelfglance

Agent endpoint

What an agent sees at juliettehasagun.com

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

ProductPriceCategorySKU
Juliette €30.00 set hb-3-2-8 PJUL100
Coffret découverte - Ode to Dullness €30.00 set hb-3-2-8 VBOXODE
Coffret découverte - Banana Rush €30.00 set hb-3-2-8-3 VBOXBAN
Juliette x Skins €30.00 set hb-3-2-8-3 PSKINS100
Lady Vengeance €30.00 set hb-3-2-8-3 PLV100
Miami Shake €30.00 set hb-3-2-8 PMIAM100
Coffret découverte - Miami Shake €30.00 set hb-3-2-8 VBOXMIAM
Powder Love €30.00 set hb-3-2-8-3 PPOW100
Coffret échantillons personnalisé €15.00 set hb-3-2-8-3 COFFRETSAMPLEV2
Superdose €30.00 set hb-3-2-8-3 PSUPER100

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.