Shelfglance

Agent endpoint

What an agent sees at shelly.com

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

ProductPriceCategorySKU
Shelly Power Strip 4 Gen4 White €59.90 set el-7-15-8 FG3800238070564
Shelly Power Strip 4 Gen4 Black €59.90 set el-7-15-8 FG3800238070571
Shelly 1 Gen3 €13.90 set ha-11-10-2 FG3800235261767
Shelly Pro 3EM €157.90 set ha-11-16-1 FG3800235268100
Shelly 1PM Gen4 €21.90 set ha-11-10-2 FG3800238070717
Shelly Plus RGBW PM €30.90 set ha-11-10-2 FG3800235265635
Shelly Pro 3EM-400 €272.90 set ha-11-16-1 FG3800235268117
Shelly 2PM Gen4 €29.90 set ha-11-10-2 FG3800238070748
Shelly Plug M Gen3 White 4-pack €37.90 set ha-10-1-5-2 FG3800238074180
Shelly Pro 3EM 3CT 63 €129.90 set ha-11-16-1 FG3800235268193

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.