Shelfglance

Agent endpoint

What an agent sees at jlindebergusa.com

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

ProductPriceCategorySKU
Janice Mid Layer / White $108.50 not set 7310427881599
Susanna Mid Layer / JL Navy $72.50 set na 7310423785860
Pinja Pant / JL Navy $170.00 set na 7310423802666
KV Polo / JL Navy $110.00 set na 7310423753401
Adina Golf Skirt / JL Navy $108.50 not set 7310428792894
Janice Mid Layer / JL Navy $108.50 not set 7310428329670
Pia Pant / JL Navy $170.00 set na 7310423799805
Ella Compression Top / Black $110.00 set na 7310423793704
Leyla Polo / Black $95.00 set na 7310423793223
Janice Mid Layer / Black $108.50 not set 7310427881643

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