WebAZ

How to shop with AI

Start with a real need, compare the evidence, then decide whether to buy.

An AI shopping assistant is most useful when it can explain why each candidate fits. This guide starts with research only: no order creation, wallet connection or payment is needed to explore the public WebAZ catalog.

1. Give the agent access to product information

Open the catalog and share a public product link with an assistant that can read webpages. For tool-based discovery, use the documented HTTP interface or read-only MCP connection supported by your client. Not every assistant supports custom tools or webpage reading.

A link or connection gives your current session a source to consult. It does not mean WebAZ products are automatically indexed by Google or included in every ChatGPT user's search results.

2. Describe the job, not just the product name

Specify your use case, must-have features, destination, quantity and budget currency. Keep a target budget separate from a confirmed delivered quote.

Illustrative read-only prompt

Find up to three travel mugs on WebAZ for a daily commute to Singapore. I want one mug, around 500 ml, that fits in a work bag. My target is S$40 delivered. Compare capacity, dimensions, material, stated leak resistance, listing currency, shipping and returns. Include product links and mark missing facts as unknown. Do not assume an item fits the budget if delivery costs are missing. Do not create an order or make a payment.

This is an example request, not a claim that matching products are currently available or that a purchase has been tested.

3. Ask three questions about the shortlist

If the agent cannot open a source, ask it to say so. Open the product page yourself or choose another candidate rather than accept invented details.

4. Keep research separate from purchase

A recommendation is not permission to spend. Before proceeding, obtain a fresh quote for the chosen variant, quantity and destination, including its expiry and unresolved costs. Ordering and payment need their own supported authorization; creating an order is not proof of payment.

Developers exploring agent payments can read the x402 integration documentation. Payment availability depends on the client and payment setup; this guide does not require or demonstrate a live payment.