Shelfglance

Agent endpoint

What an agent sees at jenis.com

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

ProductPriceCategorySKU
Goat Cheese with Red Cherries $17.00 set fb-2-9-1-3 118B
Strawberry Buttermilk $17.00 set fb-2-9-1-3 1030B
Savannah Buttermint $17.00 set fb-2-9-1-3 141C
High Five Candy Bar $17.00 set fb-2-9-1-3 1076b
Brown Butter Almond Brittle $17.00 set fb-2-9-1-3 108B
Sweet Cream Biscuits & Peach Jam $17.00 set fb-2-9-1-3 154B
Gooey Butter Cake $17.00 set fb-2-9-1-3 175E
Brambleberry Crisp $17.00 set fb-2-9-1-3 106C
Salty Caramel $17.00 set fb-2-9-1-3 139B
Darkest Chocolate $17.00 set fb-2-9-1-3 116B

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.