Shelfglance

Agent endpoint

What an agent sees at toms.com

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

ProductPriceCategorySKU
Alpargata All Black Heritage Canvas $50.00 set na 195703480096
Carolina Mary Jane Espadrille Dark Sky Textured Denim $85.00 set na 195703629457
Alpargata Navy Heritage Canvas $50.00 set na 195703480874
Womens Alpargata Mary Jane Black Canvas $60.00 set na 195703865985
Womens Carolina Mary Jane Espadrille Natural Leopard Print $85.00 set na 195703818738
Diana Mule Wedge Sandal Black Leather $90.00 set na 195703667657
Carolina Lace-Up Espadrille White Onyx Textured Denim $85.00 set na 195703626593
Diana Mule Black Sandal $80.00 set na 195703334108
Carolina Lace-Up Espadrille White Beachside Woven $80.00 set na 195703630231
Alpargata Red Heritage Canvas $50.00 set na 195703480744

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.