Shelfglance

Agent endpoint

What an agent sees at alastin.com

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

ProductPriceCategorySKU
Restorative Skin Complex with TriHex+™ $258.00 set hb-3-2-9-2 162
Ultra Light Moisturizer with TriHex Technology® $98.00 set na 242
Ultra Nourishing Moisturizer with TriHex Technology® $98.00 set na 225
HydraTint Pro Mineral Broad Spectrum Sunscreen SPF 36 $84.00 set hb-3-2-9-15 408
Restorative Eye Complex with TriHex Technology® $128.00 set hb-3-2-9 452
HA (Hyaluronic Acid) IMMERSE Serum™ $134.00 set na 552
Renewal Retinol $81.00 set na 657
Restorative Neck Complex with TriHex Technology® $158.00 set hb-3-2-9 233
C-RADICAL Defense Antioxidant Serum $218.00 set hb-3-2-9 372
Gentle Cleanser $58.00 set hb-3-2-9-6 307

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.