Agent endpoint
What an agent sees at gestalten.com
Searching gestalten.com for gestalten the way a shopping agent would returned 10 products. This is what it received.
| Product | Price | Category | SKU |
|---|---|---|---|
| LAND | €60.00 | set me-1-3 |
4224 |
| Designed to Stay: The Design Hotels™ Book | €60.00 | set me-1-3 |
4194 |
| The Touch | €70.00 | set me-1-3 |
4184 |
| Baked In | €45.00 | set me-1-3 |
4243 |
| The New Mediterranean | €45.00 | set me-1-3 |
5981 |
| Cabin Fever | €45.00 | set me-1-3 |
4030 |
| Whatever the Weather | €19.90 | set me-1-3 |
4711 |
| Flex Appeal | €40.00 | set me-1-3 |
4238 |
| Northern Exposure | €50.00 | set me-1-3 |
4226 |
| Surf Shacks Vol. 3 | €60.00 | set me-1-3 |
4216 |
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.