Shelfglance

Agent endpoint

What an agent sees at kytebaby.com

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

ProductPriceCategorySKU
Sleep Bag in Sage 2.5 $60.00 set aa-1-25-6 1501SG1
Sleep Bag in Taro 1.0 $55.00 set aa-1-25-6 1402TA0
Zippered Footie in Atlantic $36.00 set aa-1-25-6 1908AC00
Sleep Bag in Small Mist Stripe 1.0 $55.00 set aa-1-25-6 1401SSMI0
Sleep Bag in Cloud 1.0 $55.00 set aa-1-25-6 1402CD0
Zippered Footie in Bow $36.00 set aa-1-25-6 1911BOWS00
Zippered Footie in Slate $36.00 set aa-1-25-6 1908SL00
Zippered Footie in Fishing $36.00 set aa-1-25-6 1911FS00
Zippered Footie in Apple Blossom $36.00 set aa-1-25-6 1908AB00
Take Me Home Set with Bow in Bow $40.00 set aa-1-25-5 1471BOWS0

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.