Shelfglance

Agent endpoint

What an agent sees at bouldernordic.com

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

ProductPriceCategorySKU
BNS Insulated Drink Belt 1L $29.75 set sg-4-10-3 210000168290
BNS Pom Hat $34.99 set aa-2-17-2 210000169964
Holmenkol Knit Cap Navy $28.99 set aa-2-17-16 210000167733
LABOR - XC Hot Box Race Harden (no scrape) $49.00 set se-6-4 210000169596
Waxless Ski Grinding Surcharge $39.00 not set 210000138744
LABOR - XC Flex Test $20.00 not set 210000138708
LABOR - XC Hot Box Service HB+ (No scrape) $39.00 not set 210000174600
BNS Ski Tie / Strap (pair) $5.00 not set 210000139494
Stone Grind $89.00 not set 210000134379
Boulder Nordic & Cycle Sport Gift Card $10.00 set gc none

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 5 of 10 carried a category and 9 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.