Shelfglance

Agent endpoint

What an agent sees at khloefemme.com

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

ProductPriceCategorySKU
Crop Top con Drappeggio €40.80 not set 88000292627
Crop Top con Drappeggio €40.80 not set 88000292629
Giacca In Pelle con Impunture €53.40 set na 88000278257
Top In Maglia con Frange Misto Mohair €44.40 not set 88000281630
Crop Top con Drappeggio €40.80 not set 88000292625
Completo Top e Gonna Effetto Pelle €59.40 not set 88000292572
Crop Top con Bottoncini €34.80 not set 88000292645
Crop Top con Bottoncini €34.80 not set 88000292643
Crop Top con Bottoncini €34.80 not set 88000292641
Crop Top con Drappeggio €40.80 not set 88000292631

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 1 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.