Shelfglance

Agent endpoint

What an agent sees at kelbournewoolens.com

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

ProductPriceCategorySKU
Perennial Minis $4.00 set ae-2-1-2-6-4 MINIPE520 RAS
Germantown DK $16.00 set ae-2-1-2-6-4 GD105 NAT
Germantown $16.00 set ae-2-1-2-6-4 GE105 NAT
Lucky Tweed $25.00 set ae-2-1-2-6-4 LU006 BLA
Scout $20.00 set ae-2-1-2-6-4 SC005 BLA
Camper $10.50 set ae-2-1-2-6-4 CA105 NAT
Cozy $24.00 set ae-2-1-2-6-4 CZ001 BLA
Harmony $16.00 set ae-2-1-2-6-4 HA105 NAT
Perennial $26.00 set ae-2-1-2-6-4 PE520 RAS
Keystone $9.00 set ae-2-1-2-6-4 KE002 JET

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.