Shelfglance

Agent endpoint

What an agent sees at hobbii.com

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

ProductPriceCategorySKU
Baby Snuggle Solid $9.20 set ae-2-1-2-6-4 9001931601
Diablo $6.80 set ae-2-1-2-6-4 9001932701
Winter Glow Solid $13.60 set ae-2-1-2-6-4 9001946101
Rainbow Lace $3.30 set ae-2-1-2-6-4 9001932801
Horizon $13.44 set ae-2-1-2-6-4 9001936301
Dahlia Halloween (Limited Edition) $16.30 set ae-2-1-2-6-4 HB-37851
Rainbow Cotton 8/8 $5.00 set ae-2-1-2-6-4 9001920401
Honey Bunny $9.60 set ae-2-1-2-6-4 HB-23812
Fantasy $4.80 set ae-2-1-2-6-4 9001937801
Tea Time XL $14.40 set ae-2-1-2-6-4 HB-34302

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.