Shelfglance

Agent endpoint

What an agent sees at locallegends.store

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

ProductPriceCategorySKU
Shining Mew [SHL - 40/73] $161.90 not set 3482354
Muk [LM - 11/92] $37.10 not set 2736880
Golem [LM - 6/92] $9.54 not set 2736799
Guardian of Faith [AFR - 18] $1.32 not set 5066541
Lost to Legend [LTR - 22] $0.15 not set 7188925
Dark Celebi [HL - 4/101] $62.46 not set 2873464
Clever Impersonator [C19 - 82] $3.69 not set 4157594
Folk Hero [CLB - 650] $4.68 not set 5653157
The Legend of Roku [TLA - 145] $10.29 not set 8976524
Sliver Queen [STH] $271.03 not set 368204

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.