Shelfglance

Agent endpoint

What an agent sees at thejewelfactor.com

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

ProductPriceCategorySKU
Pink Royal Necklace AED 205.00 set aa-6-8 none
Spring Earrings AED 95.00 set na E04102
Rain Huggies (White) AED 45.00 set aa-6-6 E0040
Dome Ring (Multi) AED 108.00 set aa-6-9 none
Tala Earrings (Blue) AED 100.00 set aa-6-6 none
Leaves of Art Ring AED 70.00 set aa-6-9 none
Palace Jewels Necklace Set AED 295.00 set na N0035
Chopar Earrings AED 139.00 set aa-6-6 none
Niloufer Necklace AED 215.00 set aa-6-8 N0033
Elysian Leaf Ring AED 109.00 set aa-6-9 R0012

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 5 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.