Shelfglance

Agent endpoint

What an agent sees at tecnifibre.com

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

ProductPriceCategorySKU
T-FIGHT 285 €229.99 set sg-1-20-7 14FI285X51
T-FIGHT 300 €249.99 set sg-1-20-7 14FI300X51
BOMBA SOFT €199.99 set sg-4-14-7-1 16BOMBASO6
TEMPO 265 V2 €74.99 set sg-1-20-7 14TEM26540
T-FIGHT 300S €259.99 set sg-1-20-7 14FI300S51
SLASH 120 POWER €199.99 set sg-1-15-6 12SLA120P5
T-FIGHT 300 IG €249.99 set sg-1-20-7 14FI300IG2
TOUR ENDURANCE SAND BACKPACK €69.99 set sg-1-20-6-2 40TOUBEIBP
TF-X1 V2 300 €187.49 set sg-1-20-7 14TFX30041
Short X-Loop Fire  €50.00 set aa-1-1 23XLOOWH61

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.