Agent endpoint
What an agent sees at infitec.com
Searching infitec.com for infitec the way a shopping agent would returned 10 products. This is what it received.
| Product | Price | Category | SKU |
|---|---|---|---|
| CCL 1000 Series | $0.00 | set na |
none |
| BOS Series | $0.00 | set na |
none |
| PCSD Series | $0.00 | not set | none |
| UMS100A Series | $0.00 | set na |
none |
| BTS Series | $0.00 | set na |
none |
| BOKR Series | $0.00 | not set | none |
| DS Series | $0.00 | set na |
none |
| ISSA Series | $0.00 | not set | none |
| DBS Series | $0.00 | set na |
none |
| QBS Series | $0.00 | not set | 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 6 of 10 carried a category and 0 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.