Shelfglance

Agent endpoint

What an agent sees at juviasplace.com

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

ProductPriceCategorySKU
LONG WEAR LIP PENCIL $6.50 set hb-3-2-6-5-3 1200495
The Nude Velvety Matte Lipstick $7.50 set hb-3-2-6-5-6 1000669
Blushed Duo Blush $20.00 set hb-3-2-6-4-1 1001611
Blushed Liquid Blush $18.00 set hb-3-2-6-4-1 1002183
The Violets Palettes $15.00 set hb-3-2-6-3-2 1000095
Nubian Earth Matte Lipstick $7.50 set na 1001991
The Nubian Palette $25.00 set na 1000097
The Chocolates Palette $15.00 set hb-3-2-6-3-2 1000093
Luxe Lip Liner $6.50 set na 1000699
Blushed Liquid BlushLighter $18.00 set hb-3-2-6-4-1 1200165

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.