Shelfglance

Agent endpoint

What an agent sees at hey-honey.com

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

ProductPriceCategorySKU
Cropped Top Black €45.00 set aa-1-1-2-1 4260490276750
Leggings Cropped Black €74.00 set aa-1-1-1-2 4262466690898
Surf Style Leggings Leo Clay €89.00 set aa-1-1-1-2 4260490277658
Biker Leo Clay €74.00 set aa-1-1-1-3 4260730090283
Cropped Top White €45.00 set aa-1-1-2-3 4260490276781
Biker Ribbed Pastel Yellow €74.00 set aa-1-1-1-3 4260730098135
Lux Bomber Jacket Black €55.00 set aa-1-10-2-2 4260730092676
Bustier Dark Lace €74.00 set aa-1-1-6 4260671823643
Racerback Bra Leo Shadow €26.00 set aa-1-1-6 4260671823469
Leggings Cropped Leo Forest €109.00 set aa-1-1-1-2 4260671821250

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.