Shelfglance

Agent endpoint

What an agent sees at ninjatransfers.com

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

ProductPriceCategorySKU
Ninja Custom Transfers $0.37 set ae-2-1-2-1-6 99888871
Custom Heat Transfers $0.37 set na 00840400528007
DTF Transfers By Size $0.37 set ae-2-1-2-1-6 00810140100436
Ninja Fast DTF Transfers $0.37 set na 00840400525549
Next Day DTF Transfers $0.37 set ae-2-1-2-1-6 00840400516868
T-Shirt Transfers $0.37 set ae-2-1-2-1-6 00840400526041
Transfers for Sweatshirts $0.37 set ae-2-1-2-1-6 00840400527031
DTF Transfers Names & Numbers $0.37 set ae-2-1-2-1-6 namesnumbers1
Transfers for Hats $0.37 set ae-2-1-2-1-6 00810140103253
Transfers for Neck Labels $0.37 set ae-2-1-2-1-6 00810140100580

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.