Shelfglance

Agent endpoint

What an agent sees at floreagarden.com

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

ProductPriceCategorySKU
Tulpan - Avant Garde SEK 99.00 set na T002
Praktvädd - Oxford Blue SEK 49.00 not set P1460095
Sommarflox - Creme Brulee SEK 49.00 set na PB1460026
Rosenskära - Apricot Lemonade SEK 69.00 set na P1460050
Blåklintmix EKO SEK 49.00 set na PB1460046
Riddarsporre - Candle Light Blue Shades SEK 69.00 set na P1460125
Luktärt - Old Times SEK 49.00 set na P1460173
Lökpaket - Våra älskade sorter SEK 789.00 set na TP009
Amarant - Viridis SEK 49.00 set na P1460079
Tulpan - Dreamer SEK 119.00 set na T017

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 9 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.