Shelfglance

Agent endpoint

What an agent sees at enve.com

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

ProductPriceCategorySKU
SES 4.5 Pro $1,700.00 set sg-4-4-2-24-4 100-3323-001
SES 4.5 $1,282.50 set sg-4-4-2-24-4 100-3319-007
AERO IN-Route Handlebar $400.00 set sg-4-4-2-9 300-1003-112
SES Road Tire $75.00 set sg-4-4-2-21 300-1022-004
Road Stem $350.00 set sg-4-4-2-17 300-1000-360
IN-Route Aero Road Stem $350.00 set sg-4-4-2-17 300-1029-018
Mountain Fork $700.00 set sg-4-4-2-5 200-2002-101
SES AR Road IN-Route Handlebar $400.00 set sg-4-4-2-9 300-1028-001
M9 Pro $1,035.00 set sg-4-4-2-24 100-2324-001
AR40 $630.00 set sg-4-4-2-23-8 100-3324-001

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.