Shelfglance

Agent endpoint

What an agent sees at beachlife.com

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

ProductPriceCategorySKU
Vanilla & Black shape bikinitop €29.95 set na BSW109B973B36
Alaskan Blue twist bikinitop €41.95 set na BSW106B651B36
Pink Shimmer twist bikinitop €29.95 set na BSW106B252B36
Green Tiger high waist bikinibroekje €17.45 set na BSW206D750034
Bright Plum triangel bikinitop €34.95 set na BSW112B552B36
Burgundy Shine strik bikinibroekje €24.45 set na BSW204A451036
Green Tiger twist bikinitop €29.95 set na BSW106B750B36
Purple Flash hoog bikinibroekje €39.95 set na BSW202A574036
Green Tiger triangel bikinitop €24.95 set na BSW112B750B36
Green Glitter bandeau bikinitop €59.95 set na BSW101C751B36

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.