Shelfglance

Agent endpoint

What an agent sees at bagsmart.com

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

ProductPriceCategorySKU
Faro 29L Travel Backpack Set $74.99 set lb-1 BM0301143AN022
Blast Pro 40L Travel Backpack $109.99 set lb-1 BM0301157AN022
Paz 20L Totepack $69.99 set lb-1 BM0305124AN007
Roamer 20" Carry On $109.99 set lb-12 BM0105016AN244
Paz 23L Backpack $69.99 set lb-1 BM0301103AN499
Focus Tote $51.99 set lb-13 BM0305134AN012
Focus 15.6" Laptop Backpack $59.99 set lb-1 BM0301149AN012
Paz 23L Tote $69.99 set lb-13 BM0305085AN499
Paz 34L Duffle $74.99 set lb-6 BM0102047AN498
REIKI Duffle $69.99 set lb-6-1 BM0102102AN353

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.