Shelfglance

Agent endpoint

What an agent sees at tiendacereza.com

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

ProductPriceCategorySKU
Set Zara COP 10,090,000 not set GCL324-UNINEG
Body Leticia Negro COP 13,300,000 not set GCL266-UNINEG
Set Amour COP 11,190,000 not set GCD447-UNINEG
Conjunto Hadar Blanco COP 9,174,000 not set GCL220B-UNIBLA
Panty Tifanny COP 5,400,000 not set GCP098-UNINEG
Set Hera Negro COP 12,490,000 not set GCL243N-UNINEG
Set Dulce Negro COP 11,690,000 not set GCL262N-UNINEG
Body Veil Negro COP 8,890,000 not set GCL338N-UNINEG
Set Snow COP 9,890,000 not set GCD444-UNIAZU
Set Patric COP 9,390,000 not set GCL264-UNIVER

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 0 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.