Shelfglance

Agent endpoint

What an agent sees at oribe.com

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

ProductPriceCategorySKU
Gold Lust Repair & Restore Shampoo $23.00 set hb-3-10-13-3 400172
Gold Lust Repair & Restore Conditioner $24.00 set hb-3-10-13-1 400103
Gold Lust Transformative Masque $28.00 set hb-3-10-2 400108
Dry Texturizing Spray $26.00 set hb-3-10-10 400129
Supershine Moisturizing Cream $24.00 set hb-3-10-10 400198
Silverati Conditioner $52.00 set hb-3-10-13-1 400031
Hair Alchemy Resilience Shampoo $20.00 set hb-3-10-13-3 401850
Supershine Hydrating Shampoo $19.00 set hb-3-10-13-3 402453
Imperméable Anti-Humidity Spray $24.00 set hb-3-10-10 400276
Hair Alchemy Resilience Conditioner $21.00 set hb-3-10-13-1 401854

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.