Shelfglance

Agent endpoint

What an agent sees at nativecos.com

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

ProductPriceCategorySKU
Moisturizing Conditioner $9.00 set hb-3-10-13-1 80715260
Facial Cleanser $13.00 set hb-3-2-9-6 80842734
Facial Moisturizer $15.00 set hb-3-2-9-20 80842837
Daily Clean Conditioner $10.00 set hb-3-10-13-1 80785213
Scalp Refreshing Conditioner $13.00 set hb-3-10-13-1 80855736
Body Scrub $10.00 set hb-3-2-1 80874758
Moisturizing Body Wash $13.00 set hb-3-2-1-5 80878985
Body Wash $11.00 set hb-3-2-1-5 80874724
Body Lotion $14.00 set hb-3-2-9-10 80788927
Moisturizing Shampoo $9.00 set hb-3-10-13-3 80715259

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.