Shelfglance

Agent endpoint

What an agent sees at barkershoes.com

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

ProductPriceCategorySKU
Glasgow - Black Hi-Shine £150.00 set aa-8 F111GW01050
Albert - Black Hi-Shine £205.00 set aa-8 664237050
Cheltenham £225.00 set aa-8 327117050
Glasgow - Black Calf £150.00 set aa-8 F111GW11050
Perth - Burgundy Hi-Shine £245.00 set aa-8 376777050
Skye - Black Grain £300.00 set aa-8 398816050
Darlington - Black Hi-Shine £205.00 set aa-8 409116050
Sullivan - Cedar Hand Painted / Navy Suede £260.00 set aa-8 471237050
Gatwick - Black Hi-Shine £150.00 set aa-8 F112GW01050
Cornhill - Black Hi-Shine £245.00 set aa-8 2599GW01050

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.