Shelfglance

Agent endpoint

What an agent sees at coffeebeancorral.com

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

ProductPriceCategorySKU
Tanzania Peaberry, Kilimanjaro $8.15 set fb-1-3 TANZPB
Costa Rica: La Minita Estate, Tarrazu $8.45 set fb-1-3 CRLAMINITA
Colombia: Supremo EP, Huila $8.45 set fb-1-3 COLHUILA
Sumatra: Tiger, Lintong $11.00 set fb-1-3 SUMTIGER
Sumatra: Mandheling G1, Aceh $9.00 set fb-1-3 SUMMAN
Java: Blawan Estate, East Java $10.55 set fb-1-3 JAVAKAYUMAS
Sumatra Lake Toba, Lintong TP $8.55 set fb-1-3 SUMTOBA
Multi Origin: Decaf Morning Glory, Multi Origin Blend $11.35 set fb-1-3 MORNGLORYSWP
Mexico: Rancho San Francisco, Chiapas $10.35 set fb-1-3 MEXSANFRAN
CBC Blend: Citrus Sting $8.85 set fb-1-3 SCORPIO

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.