Shelfglance

Agent endpoint

What an agent sees at daisonet.com

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

ProductPriceCategorySKU
毛糸(ドールズヤーン、ブラック)30g ¥110 not set 4550480759784
毛糸(ドールズヤーン、ブルー)30g ¥110 not set 4550480759739
毛糸(ドールズヤーン、ブラウン)30g ¥110 not set 4550480759791
毛糸(ドールズヤーン、イエロー)30g ¥110 not set 4550480759760
毛糸(ドールズヤーン、ピンク)30g ¥110 not set 4550480759753
毛糸(ドールズヤーン、レッド)30g ¥110 not set 4550480759746
毛糸(ドールズヤーン、ベージュ)30g ¥110 not set 4550480759777
毛糸(ドールズヤーン、ホワイト)30g ¥110 not set 4550480759722
毛糸(ドールズヤーン、グリーン)30g ¥110 not set 4550480759715

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 0 of 9 carried a category and 9 of 9 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.