Shelfglance

Agent endpoint

What an agent sees at newyorkdress.com

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

ProductPriceCategorySKU
Ladivine CC0389 Dress $267.00 not set ladivine-cc0389-black-nude-0
Ladivine CD295 Dress $225.00 set na ladivine-cd295-black-0
Ladivine CD387 Dress $175.00 set na ladivine-cd387-black-2
Ladivine C161 Dress $147.00 set na ladivine-c161-black-0
Ladivine CD791 Dress $139.00 set na ladivine-cd791-black-0
Ladivine CC324 Dress $289.00 set na ladivine-cc324-black-nude-2
Hot Contact 5245 Dress $288.00 not set hot-contact-5245-black-6
Ladivine CC341 Dress $279.00 set na ladivine-cc341-blush-4
Hot Contact 8446CL Dress $209.00 set na hot-contact-8446cl-black-6
Ladivine 7448 Dress $139.00 set na ladivine-7448-black-2

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