Shelfglance

Agent endpoint

What an agent sees at rockabyebabymusic.com

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

ProductPriceCategorySKU
Lullaby Renditions of The Rolling Stones $9.99 set me-3 CD 9629
Lullaby Renditions of Eminem - Vinyl $30.00 set me-3-6 LP 9703
Not So Silent Night - CD Bundle $35.00 set me-3-3 NOT BUN
Lullaby Renditions of Blink-182 - Vinyl $30.00 set me-3-6 LP 9708
Lullaby Renditions of Fleetwood Mac $9.99 set me-3 CD 9710
Lullaby Renditions of The Flaming Lips $9.99 set me-3 CD 9681
Lullaby Renditions of Radiohead $9.99 set me-3 CD 9603
Lullaby Renditions of Katy Perry $9.99 set me-3 CD 9737
Lullaby Renditions of Metallica $9.99 set me-3 CD 9600
Lullaby Renditions of Ed Sheeran $9.99 set me-3 CD 9746

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.