Shelfglance

Agent endpoint

What an agent sees at flooringstores.com

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

ProductPriceCategorySKU
Manor in Revere Oak $5.00 set na WO401-F1711
Manor in Charter Oak $5.00 set na WO401-F1710
Manor in Shaker Oak $5.00 set na WO401-F1712
Refined Timbers in River Street $3.00 set ha-2-5 N-20500 10014-UW
Eastport in Jersey Shore $3.00 not set LHAC387JS
Carver in Harris Street $3.00 set ha-2-5 N-20520 12205-UW
Refined Timbers in Broughton Street $3.00 set ha-2-5 N-20500 10012-UW
Points East in Chimney Rock $3.00 not set PE127CR
Everlasting in Honeyburge $3.00 not set PM-EKDP74L66WEE-AH
Eastport in Boca Grande $3.00 set ha-2-5 LHAC387BG

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