Shelfglance

Agent endpoint

What an agent sees at native-instruments.com

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

ProductPriceCategorySKU
Session Guitarist - Acoustic Sunburst Deluxe €149.00 set so-1-10-8 34092
Kontakt 8 €99.00 set so-1-10-8 34259
Komplete 26 Standard €149.00 set so-1-10-8 37182
Cremona Quartet Solo €199.00 set so-1-10-8 27467
Symphony Essentials - Collection €299.00 set so-1-10-8 24825
Stradivari Cello €199.00 set so-1-10-8 28407
Session Strings 2 €49.00 set so-1-10-8 25612
Maschine 3 including Maschine Central €79.00 set so-1-10-8 35603
Reaktor 6 €99.00 set so-1-10-8 23809
Session Horns €99.00 set so-1-10-8 22280

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.