Shelfglance

Agent endpoint

What an agent sees at preworn.com

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

ProductPriceCategorySKU
Preworn Womens Blue Pullover Jumper Size S £12.50 not set Q100601222
Preworn Unisex Green Scarf £6.50 not set Q100923539
Preworn Womens Blue Pullover Jumper Size XL £12.50 not set Q101941618
Preworn Womens White Pullover Jumper Size S £12.50 not set Q101635616
Preworn Mens Black T-Shirt Size S £6.50 not set Q101636345
Preworn Mens Blue T-Shirt £6.50 not set Q101845612
Preworn Mens Blue Jacket Suit Jacket Size 36 £70.00 not set Q100783677
Preworn Womens Black Bodycon Size XS £10.50 not set Q101706729
Preworn Mens Blue Pullover Casual £10.50 not set Q101618518
Preworn Womens Black Jacket Size 40 £28.50 not set Q100966007

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