Shelfglance

Agent endpoint

What an agent sees at loveamika.com

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

ProductPriceCategorySKU
the kure | intense strength repair mask $14.00 set hb-3-10 AM50.20522
amika on-the-go | signatures + accessories set $94.00 set hb-3-10-1 AM41.22224
everyday magic | bestsellers set $32.00 set hb-3-10-13-2 AM41.21466
soon-to-be fave | signature sweatshirt $55.00 set aa-1-13-13 AM80.20935
hydro rush | intense moisture shampoo $13.00 set hb-3-10-13-3 AM50.19086
amika:aura | hair and body mist $28.00 set hb-3-2-8 AM50.22062
the wizard | detangling primer $16.00 set hb-3-10-10 AM50.20589
normcore | signature conditioner $10.00 set hb-3-10-13-1 AM50.18495
the kure | strength repair conditioner $13.00 set hb-3-10-13-1 AM50.18505
gift card | amika $10.00 set gc AM50.GIFT10

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.