Shelfglance

Agent endpoint

What an agent sees at felco.com

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

ProductPriceCategorySKU
FELCO 6 - Customizable CHF 84.90 set hg-12-1-7-9 1 001 006 11
FELCO 8 - Customizable CHF 84.90 set na 1 001 008 11
FELCO 8 Premium SE CHF 249.90 set na 1 001 008 02
FELCO 310 CHF 20.80 set na 1 001 310 03
FELCO 834W CHF 716.70 set na 1 001 834 01
FELCO 6 Elite CHF 89.90 set na 1 001 006 05
FELCO 290 CHF 189.90 set na 1 001 290 01
FELCO 9 CHF 71.90 set na 1 001 009
FELCO 290-4M CHF 259.90 set na 1 001 290 02
FELCO 834V LEFT HANDED CHF 716.70 set na 1 001 834 04

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.