Shelfglance

Agent endpoint

What an agent sees at aputure.com

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

ProductPriceCategorySKU
LS 60x $419.00 set co-4-2 APA0183A20
STORM 80c $599.00 set co-4-2 AP00336A20
STORM 700x Cine Kit $2,140.00 set co-4-2 AG0700047X
LS 600c Pro II $1,490.00 set co-4-2 AP00000215-APA0172A30
MC Pro $199.00 set co-4-2 APA0229A10
MT Pro $199.00 set co-4-2 APA0202A10
LS 300d II $759.00 set co-4-2 APA0129A2F
STORM 1200x $2,990.00 set co-4-2 AP20334A20
Accent B7c $70.00 set co-4-2 APC0146A7B
STORM 400x $1,059.00 set co-4-2 AP00339A20

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.