Shelfglance

Agent endpoint

What an agent sees at gruns.co

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

ProductPriceCategorySKU
Popsicle® Firecracker Grüns $70.38 set hb-1-9-6-7 333701
Grüns Raspberry Lemonade $70.38 set hb-1-9-6-7 334001
Grüns $66.65 set hb-1-9-6-7 333001
Grüns Minions $70.38 set hb-1-9-6-7 335005
Grüns Kids $53.32 set hb-1-9-6-7 333005
Popsicle® Firecracker Grüns Kids $57.05 set hb-1-9-6-7 333705
Grüns Kids Raspberry Lemonade $57.05 set hb-1-9-6-7 334005
Grüns Kids Minions $57.05 set hb-1-9-6-7 335001
Upgrade to Quarterly on Next Order $0.00 set hb-1-9-6 60003
Upgrade to Quarterly on Next Order $0.00 set hb-1-9-6 61001

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.