Shelfglance

Agent endpoint

What an agent sees at blossom39.com

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

ProductPriceCategorySKU
ショッピングバッグ(大)ブラック ¥110 set ae-3-1-5-1 none
ショッピングバッグ(小)ピンク ¥55 set ae-3-1-5-1 none
ショッピングバッグ(大)ピンク ¥110 set ae-3-1-5-1 none
ギフトカード ¥1,000 set gc none
ラッピング(大型商品はリボンのみ) ¥330 set ae-3-1-5 none
メッセージカード ¥0 set ae-3-1-6 message-card-balloon
ダイパーケーキ - バスタイム アイボリー ¥7,700 set bt-2 3939057010311
ダイパーケーキ - バスタイム ブルー ¥7,700 set bt-2 3939057010304
ダイパーケーキ - バスタイム ピンク ¥7,700 set bt-2 3939057010298
ダイパーケーキ - bib&softtoy giraffe ¥9,350 set bt-2 3939057010441

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