Shelfglance

Agent endpoint

What an agent sees at mymuesli.com

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

ProductPriceCategorySKU
Glutenfree Chocolate Müsli €10.95 set fb-2-11-4 100156602
Blueberry Müsli €9.95 set fb-2-11-4 100192202
Super Choc Müsli €8.95 set fb-2-11-4 100224507
Berry Müsli €9.95 set fb-2-11-4 100190403
Chocolate Müsli €8.95 set fb-2-11-4 100224304
Honey Nuts Müsli €9.95 set fb-2-11-4 100192102
Glutenfree Berry Müsli €9.95 set fb-2-11-4 100156402
Blueberry Cassis Crunchy Granola €12.95 set fb-2-11-4 100336800
Strawberry Cheesecake Müsli €9.95 set fb-2-11-4 100161302
Chocolate Hazelnut Almond Granola €12.95 set fb-2-11-4 100214503

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.