Shelfglance

Agent endpoint

What an agent sees at igloocoolers.com

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

ProductPriceCategorySKU
Trailmate® 50 Qt Cooler $95.99 set hg-11-3-3 00050859
Trailmate® 25 Qt Cooler $79.99 set hg-11-3-3 00033130
Trailmate® Journey 70 Qt Cooler $229.99 set hg-11-3-3 00035161
Trailmate® 52 Qt Roller Cooler $127.99 set hg-11-3-3 00035110
Tag Along Too Cooler $39.99 set hg-11-3-3 00033218
ICF 18 $359.99 set hg-11-3-3 00050727
Retro Playmate Mini 4 Qt Cooler $22.99 set hg-11-3-3 00048535
Retro Little Playmate 7 Qt Cooler $27.99 set hg-11-3-3 00033309
Trailmate® 75 Qt Roller Cooler $179.99 set hg-11-3-3 00035111
Polar 120 Qt Cooler $129.99 set na 00044577

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.