Shelfglance

Agent endpoint

What an agent sees at madecentro.com

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

ProductPriceCategorySKU
Servicio de diseño proyecta 5 muebles para hogares COP 15,429,972 set na SERDISENO05
Servicio de 1 diseño proyecta para hogares COP 3,736,999 set na SERDISENO1
Servicio de corte a medida de tableros 1 a 15 COP 200 set na SERM0115
Corte cubo modular COP 92,400 set na SCUBMDLAR1
Corte cubo modular con perforación COP 149,900 set na SCUBMDLAR2
Corta cubo modular con perforación Y avellanad COP 166,300 set na SCUBMDLAR3
Servicio de engruese completo tipo sánduche COP 1,993,100 set na SERVREME
Servicio de corte circular interno y externo COP 1,164,300 set na CSCIRCULO
Servicio de calado interno en tableros COP 1,397,200 set na CSCALADO
Servicio corte perfil estructura aluminio COP 1,350,700 set na SCESTRAL

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.