Shelfglance

Agent endpoint

What an agent sees at thehorse.co

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

ProductPriceCategorySKU
Clementine Bag: Taupe Pebbled Leather $299.95 set na CLE17
Mini Clementine: Black Gold $249.95 set na MCL1-G
Mini Clementine Bag: Charcoal Pebbled Leather with Gold $249.95 set na MCL8
Clementine Bag: Tan Pebbled Leather $299.95 set aa-5-4 CLE2
Clementine Bag: Black Pebbled Leather with Gold $299.95 set na CLE1-G
Clementine Bag: Coffee Pebbled Leather $299.95 set na CLE3
Clementine Bag: Black Pebbled Leather $299.95 set na CLE1
Mini Clementine Bag: Tan Pebbled Leather $249.95 set na MCL2
Sporty Crossbody: Olive $119.95 set aa-5-4-7 LSC15
Florence Tote: Black $199.95 set na FL1

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.