Shelfglance

Agent endpoint

What an agent sees at tonyschocolonely.com

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

ProductPriceCategorySKU
milk almond honey nougat 32% €0.00 set fb-2-3-2 8717677339976
extra dark chocolate 70% €0.00 set fb-2-3-2 8717677339990
dark chocolate 70% €0.00 set fb-2-3-2 858010005054
milk chocolate 32% €0.00 set fb-2-3-2 8717677339792
milk caramel sea salt 32% €0.00 set fb-2-3-2 8717677339815
milk caramel sea salt 32% €0.00 set fb-2-3-2 8717677339938
milk almond honey nougat 32% €1.24 set fb-2-3-2 8720701141513
dark milk brownie 42% €0.00 set fb-2-3-2 8719956498138
milk chocolate 32% €0.00 set fb-2-3-2 8717677339914
dark almond sea salt 51% €0.00 set fb-2-3-2 8717677339853

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.