Shelfglance

Agent endpoint

What an agent sees at naysbaits.com

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

ProductPriceCategorySKU
Nays GHST €10.99 set sg-4-6-13-1-10 BS009080001
Nays GHST JNR €6.99 set sg-4-6-13-1-10 BS016035001
Nays VNM €8.99 set sg-4-6-13-1-10 BS030020001
Nays TWN €10.99 set sg-4-6-13-1-10 BS012060001
Nays PRDTR 2.0 €7.99 set sg-4-6-13-1-10 BS180035001
Nays TRN 190 €59.99 set sg-4-6-13-1-8 BH140190020
Nays BG €7.99 set sg-4-6-13-1 BS017020005
Nays MZ RNNR L 2.0 €13.99 set sg-4-6-13-1-6 BH0221401
Nays NDL €7.99 set sg-4-6-13-1-10 BS070035001
Nays SPLT €6.99 set sg-4-6-13-1-10 BS050035001

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.