Shelfglance

Agent endpoint

What an agent sees at giesswein.com

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

ProductPriceCategorySKU
Wool Sneaker Men €119.95 set na 74-10-49316-011-40
Wool Sneaker Women €119.95 set na 74-10-49315-022-36
Merino Jump Women €159.95 set na 84-10-49390-360-36
Merino Barefoot Women €149.95 set na 77-10-49336-022-36
Wool Peak Women €169.95 set na 76-10-49319-022-36
Merino Wool Knit Women €159.95 set na 72-10-49309-017-36
Merino Jump Men €159.95 set aa-8-8 84-10-49391-016-40
Merino Runners MEN €149.95 set aa-8-8 68-10-49301-026-40
Merino Runners WOMEN €149.95 set aa-8-8 68-10-49300-031-36
Merino Curve Max Women €159.95 set na 82-10-49373-310-36

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.