Shelfglance

Agent endpoint

What an agent sees at engwe.com

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

ProductPriceCategorySKU
L20 3.0 Pro €1,699.00 set sg-4-4-3-5 EUL2030PROBLACK
ENGWE N1 Air €1,249.00 set sg-4-4-3-5 EUN1AIRSTGRAYHydraulic
ENGWE P20 €999.00 set sg-4-4-3-2 EUP20Black
ENGWE M1 €1,099.00 set vp-2-2-3 EUM1BlueSingleBatteryInter
Engine Pro 2.0 €1,399.00 set sg-4-4-3-5 EUENGINEPRO2.0BL
ENGWE E26 €1,499.00 set sg-4-4-3-2 EUE26STGalaxyGrey
L20 3.0 Boost €1,399.00 set sg-4-4-3-5 EUL2030BOOSTBALCK
ENGWE M20 €1,099.00 set vp-2-2-3 EUM20White13ah
ENGWE N1 Pro €1,599.00 set sg-4-4-3-5 EUN1PROGREEN
L20 Boost €1,149.00 set sg-4-4-3-2 EUL20BoostBlack

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.