Shelfglance

Agent endpoint

What an agent sees at mac-jeans.com

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

ProductPriceCategorySKU
DREAM WIDE €109.95 set na 4069121413072
BOBBIE €79.95 set na 4069121551934
BOBBIE €79.95 set na 4069121552016
DREAM WIDE €109.95 set na 4069121412358
DREAM SUMMER €69.95 set na 4069121416943
DREAM SUMMER €99.95 set na 4069121416769
MELANIE €89.95 set na 4069121402748
DREAM BOOT authentic €109.95 set na 4069121411450
DREAM WIDE cropped €99.95 set na 4069121411818
Arne Pipe €99.95 set na 4069121426249

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.