Shelfglance

Agent endpoint

What an agent sees at nextlevelapparel.com

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

ProductPriceCategorySKU
Tri-Blend T-Shirt $5.82 set na 6010_XS_V005
CVC T-Shirt $4.23 set na 6210_XS_C103
CVC T-Shirt $4.23 set na 6210_XS_B001
CVC T-Shirt $4.23 set na 6210_XS_S172
Tri-Blend T-Shirt $5.82 set na 6010_XS_V019
CVC T-Shirt $4.23 set na 6210_XS_E001
Tri-Blend T-Shirt $5.82 set na 6010_XS_B001
Tri-Blend T-Shirt $5.82 set na 6010_XS_G011
Cotton T-Shirt $4.13 set na 3600_XS_D034
Cotton T-Shirt $4.13 set na 3600_XS_B001

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.