Shelfglance

Agent endpoint

What an agent sees at brewdog.com

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

ProductPriceCategorySKU
Brewdog Mixed Pack £16.99 set na 10000-C12330
Punk IPA £5.52 set na 10101-C64330-V2
Summer Mixed Pack £11.89 set na 10000-C10330-SMP
Wingman AF £5.49 set na 19755-C64330
Speedbird OG £1.79 set na 10123-C24330
Elvis Juice £6.29 set na 10207-C64330
Hazy Jane £5.52 set na 10118-C64330
Cold Beer Lager £4.49 set na 12160-C64440
Wingman £5.52 set na 10125-C64330
Black Heart £6.49 set na 10122-C64440

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.