Shelfglance

Agent endpoint

What an agent sees at alpinestars.com

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

ProductPriceCategorySKU
Supertech R10 Solid Helmet $1,149.95 set vp-1-6-1-7 8059347340999
SP-3 Gloves $109.95 not set 8059347542188
SMX-1 Air V2 Gloves $79.95 set vp-1-6-1-3 8033637055725
SP-8 V3 Gloves $124.95 not set 8059175359651
SMX-6 V3 Boots $349.95 not set 8059347395548
SMX S Boots $299.95 set na 8021506618706
SMX S Boots $299.95 set na 8021506618553
Faster-4 Shoes $199.95 set na 8059347532677
Supertech R Vented Boots $649.95 set vp-1-6-1 8059175376696
SM3 Solid Helmet ECE06/DOT $229.95 set vp-1-6-1-7-4 8059347571195

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