Build a multi-merchant comparison shopper that normalizes product attributes across stores

domain: agentic-commerce · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Define a canonical product schema (name, brand, model_number, price, currency, shipping_estimate, availability, merchant_id, url) that all merchant adapters must emit.
  2. Write a per-merchant adapter that fetches product data from that merchant's preferred interface (API, feed, or schema.org markup) and maps it to the canonical schema.
  3. Implement a product matching step: use a combination of exact GTIN/MPN match and fuzzy title similarity to cluster results that represent the same physical product across merchants.
  4. Compute a total-cost-of-ownership estimate per merchant offer: price + shipping + estimated tax; sort by this computed field for apples-to-apples comparison.
  5. Surface comparison results as a structured payload with merchant name, offer URL, total cost, availability, and return policy summary so an upstream agent can make or recommend a purchase decision.
  6. Store comparison results with a TTL and invalidate on receipt of a price-change event from your monitoring pipeline.

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans