Shelfglance

Agent endpoint

What an agent sees at omnes.com

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

ProductPriceCategorySKU
Francoise Dress in Magenta Blurred Floral £39.60 set aa-1-4 5056514980104
Aurelia Dress in Cerise £59.40 set aa-1-4 5056804213950
Aurelia Dress in Raspberry / Red £59.40 set aa-1-4 5056804261562
Ginny Dress in Chocolate £79.00 set aa-1-4 5056514993043
Francoise Dress in Lavender £29.00 set aa-1-4 5056514980210
Alessia Dress in Egg Yolk Yellow £29.00 set aa-1-4 5056804207553
Iris Maxi Dress in Ivory £29.00 set aa-1-4 5056804214292
Nova Tie Back Dress in Emerald Green £110.00 set aa-1-4 5056514991506
Iris Jacquard Dress in Blue £110.00 set aa-1-4 5056804211390
Nova Tie Back Dress in Magenta £110.00 set aa-1-4 5056514982511

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.