Shelfglance

Agent endpoint

What an agent sees at poppyandpeonies.com

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

ProductPriceCategorySKU
Mini Downtown Black CA$99.00 set aa-5-4-7 30176
DOWNTOWN CROSSBODY black CA$125.00 set aa-5-4-19 30138
Out and About Heritage Green CA$89.00 set aa-5-4-7 40209
the SIDEKICK blush CA$89.00 set aa-5-4-7 50022
the EVERYDAY CROSSBODY blush CA$119.00 set aa-5-4-7 30152
Mini Downtown chestnut CA$99.00 set aa-5-4-7 30210
the SIDEKICK navy CA$89.00 set aa-5-4-7 50037
the EVERYDAY CROSSBODY berry CA$119.00 set aa-5-4-7 30187
Out and About Black CA$89.00 set aa-5-4-7 40171
the SIDEKICK chestnut CA$89.00 set aa-5-4-7 50057

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.