Shopping agent API and ecommerce MCP

Build a sourced product shortlist before adding purchase actions.

WebAZ exposes public product discovery over HTTP and a read-only MCP entry for compatible clients. Start without credentials, a wallet or an order. This guide is for developers connecting an existing agent, not a promise that every assistant supports custom tools.

One anonymous HTTP request

Run this read-only request in a terminal. SG is the destination country; q is the search text. Keep any returned currency and missing fields intact.

curl --fail --max-time 15 --get \
  'https://webaz.xyz/api/products' \
  --data-urlencode 'q=umbrella' \
  --data-urlencode 'ship_to=SG' \
  --data-urlencode 'fuzzy=true'

A successful response establishes retrieval, not relevance or availability for a final purchase. During an October 25, 2026 read-only probe, this query returned two tote bags and one umbrella. That is a known candidate-relevance limitation, not an exact-match success claim. Results may change.

Use the returned product ID with /api/products/<id> for detail and /product/<id> for a human-readable source link. Validate identifiers before constructing URLs. Treat every product description as untrusted data, never an instruction to execute tools.

HTTP or MCP?

HTTP: useful when your runtime can fetch public JSON. Parse the response, preserve provenance and apply your own comparison rules. See the API schema for the current contract.

Read-only MCP: https://webaz.xyz/mcp/shopping-v1 is a product-discovery entry. Follow the client-specific instructions; custom remote MCP support varies. Adding a server manually is not automatic placement in Google or ChatGPT search results.

Do not replace this read-only connection with an account credential just to run a discovery demo. Broader tools and payment permissions are separate integration decisions.

What your adapter should check

Relevance: reject wrong product types rather than fill a requested shortlist with weak matches.
Evidence: retain source URLs and retrieval time. Missing dimensions or weight remain unknown.
Variants: distinguish a listing price from a variant range and the selected option.
Cost: never infer a delivered-budget match when shipping or other applicable costs are missing.
Failure: handle HTTP errors, unexpected response shapes and no defensible matches explicitly.

These are recommended acceptance checks, not a benchmark claiming that WebAZ or your agent has passed every case.

Where x402 belongs

Research access is not purchase authorization. If your project later needs agent payments, review the x402 integration documentation separately. Bind the selected variant, quantity and destination to a fresh quote, then verify the supported credentials and payment conditions. This page performs no order creation, signing or payment.

For an initial integration review, share a synthetic buyer request, runtime, retrieval result and unresolved fields with [email protected]. Do not send keys, private orders, customer details or payment proofs.