Shelfglance

Agent endpoint

What an agent sees at bodyandfit.com

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

ProductPriceCategorySKU
Smart Protein €35.99 set hb-1-9-6-8 1089792
All In One €32.99 set hb-1-9-6-8 1146273
Perfection Whey €34.99 set hb-1-9-6-8 1089985
Protein Drink €2.79 set hb-1-9-6-8 1156003
Whey Essential €18.49 set hb-1-9-6-8 1117501
Perfection Protein Bar €24.99 set hb-1-9-6-8 1098956
High Fibre Protein Bar €24.99 set hb-1-9-6-8 1158470
Ripped! €14.99 set hb-1-9-6-8 1089281
Whey Isolate XP €41.99 set hb-1-9-6-8 1089602
Protein Wraps €4.99 set hb-1-9-6-8 1089481

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.