Shelfglance

Agent endpoint

What an agent sees at lilyandfox.com

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

ProductPriceCategorySKU
Lipstick Pink (Glitter) $2.99 set hb-3-2 A0449
Cherry Kisses $2.99 set hb-3-2 T0331
Sea Fairy $2.99 set hb-3-2 T3620
Cranberry Sparkle $2.99 set hb-3-2 T2920
Tree-Rex $2.99 set hb-3-2 T0503
Cinderella's Slippers $2.99 set hb-3-2 T3532
Jet Set $2.99 set hb-3-2 A0056
Burlesque $2.99 set hb-3-2 A0026
Aqua Sparkles $2.99 set hb-3-2 T5793
A Twinkle In Her Eye $2.99 set hb-3-2 T4654

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.