Shelfglance

Agent endpoint

What an agent sees at bendavis.com

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

ProductPriceCategorySKU
Short Sleeve Striped 1/2 Zip Shirt - Hickory $46.00 not set 715044108406
Original Ben's Pants - Khaki $52.00 set na 715044695210
Gorilla Cut Pants - Light Grey $52.00 set na 715044677223
Lined Vest - Black $74.00 not set 715044294406
Short Sleeve Striped 1/2 Zip Shirt - Butcher Stripe $46.00 not set 715044109410
Gorilla Cut Pants - Navy $52.00 set na 715044678220
Gorilla Cut Pants - Black $52.00 set na 715044674222
Gorilla Cut Pants - Black Denim $52.00 set na 715044673225
Gorilla Cut Pants - Indigo Denim $52.00 set na 715044676226
Gorilla Cut Pants - Brown $52.00 set aa-1-12-4 715044679227

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