Shelfglance

Agent endpoint

What an agent sees at theroyalepeacock.com

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

ProductPriceCategorySKU
Ron Navy Blue Suede Leather Penny Loafer ₹5,999.00 set aa-8 2076
Cyrus Summer Navy Blue Suede Loafer ₹5,999.00 set aa-8 2132
James Black Penny Loafer ₹5,999.00 set aa-8 2005
James Brown Penny Loafer ₹5,999.00 set aa-8 2006
Felix Black Penny Loafer ₹5,999.00 set aa-8 2152
Theodore Beige Suede & Tan Wingtip Oxford ₹6,699.00 set aa-8 1630
Arthur Black Wingtip Oxford ₹6,699.00 set aa-8 1621
Bentley Black Tassel Loafer ₹5,999.00 set aa-8 2151
Fiery Tan Leather Oxford for Women ₹5,999.00 set aa-8 W1206
Marcus Dark Brown Oxford ₹6,699.00 set aa-8 1115

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.