Shelfglance

Agent endpoint

What an agent sees at inuit.com

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

ProductPriceCategorySKU
Inuk Figure CA$30,000.00 set na LM241236
Inuk, 1993 CA$475.00 set na GX250914
Hunter Throwing Harpoon CA$18,000.00 set na LM241230
Sitting Woman CA$850.00 not set GX241120
Inukshuk CA$750.00 set na CD260311
Young Inuk CA$300.00 set na PP200926
Inukshuk CA$750.00 set na NN260214
Bear CA$350.00 not set GX230401
Pangnirtung Hat (Light Green) CA$175.00 set na NN260224
Pangnirtung Hat (Light Blue) CA$175.00 set na NN260225

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