Shelfglance

Agent endpoint

What an agent sees at negativeunderwear.com

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

ProductPriceCategorySKU
Whipped High Rise in Black $45.00 set na NK-108-01F-0
Sieve Dipped Brief in Black $38.00 set na NK-100-01D6-0
Sieve Thong in Buff + White $32.00 set na NK-100-26D-0
Sieve Thong in Black $32.00 set na NK-100-01D-0
Sieve Thong in Buff $32.00 set na NK-100-06D-0
Whipped French Cut Brief in Black $45.00 set na NK-108-01FC-0
Whipped French Cut Brief in White $45.00 set na NK-108-02FC-0
Cloud Cotton French Cut Brief in Deep (Pack) $62.00 set na NK-104-087FC-01-3
Whipped French Cut Brief in Black + White $45.00 set na NK-108-122FC-0
Whipped Long Underwear in Black $110.00 set na NK-108-01W-0

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.