Shelfglance

Agent endpoint

What an agent sees at fillingspaces.com

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

ProductPriceCategorySKU
Winfleur $20.00 set ae-2-1-2-14-2 none
Etna - NEW* $20.00 set ae-2-1-2-14-2 none
Titli Sand $120.00 not set titlisand18x18-c
Nisa Romesco $120.00 set na NisaRomesco18x18-c
Trulli - NEW* $20.00 set ae-2-1-2-14-2 none
Calluna $130.00 set na calluna22x22-c
Catania Coco $120.00 set na CataniaCoco18x18-c
Majhi Sand $110.00 not set none
Mersin Cove $120.00 set na MersinCove18x18-c
Tulip Sand $110.00 not set Tulipsand18x18-c

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 7 of 10 carried a category and 6 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.