Shelfglance

Agent endpoint

What an agent sees at tyaani.com

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

ProductPriceCategorySKU
Tanisha Polki Necklace ₹364,500.00 not set TN260141
Tanisha Polki Necklace ₹357,000.00 not set TN260415
Runali Polki Necklace ₹644,200.00 set aa-6-8 JDN80336
Aliana Polki Necklace ₹293,200.00 set aa-6-8 TN00353
Titania Polki Necklace ₹442,750.00 set aa-6-8 TN00810
Heena Polki Necklace ₹341,400.00 set aa-6-8 TN00354
Tanisha Polki Necklace ₹349,600.00 set aa-6-8 TN260090
Diamond Necklace ₹309,300.00 set aa-6-8 NECK00103
Riya Polki Necklace ₹405,600.00 set aa-6-8 TYNK11056
Jonnah Polki Necklace ₹1,702,400.00 set aa-6-8 TYNK10088

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.