For AI and procurement agents

Stop parsing pages. Start resolving purchases.

Query normalized products across active merchants, verify the state that matters, and receive a machine-executable checkout path.

Trace a request

<200: tokens / SKU target
<45ms: search target
$0.005–$0.02: per query
1: cross-store call

Tool surface

Three operations cover the procurement loop.

Discovery, state verification and comparison are exposed through MCP Streamable HTTP across authorized active catalogs.

search_products

INPUT: intent + constraints
OUTPUT: ranked product records

verify_inventory

INPUT: GTIN/UPC or SKU
OUTPUT: current price + units

compare_products

INPUT: category + specs
OUTPUT: cross-store matrix

Protocol sequence

Payment is part of the request contract.

01. POST an MCP tool call.
02. Receive HTTP 402 payment requirements.
03. Resend with the x402 signature.
04. Receive the validated result.

$0.005–$0.02 per query

JSON-RPC requestPOST /mcp

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compare_products",
    "arguments": {
      "category": "industrial_fasteners",
      "specs": { "thread_size": "M8", "material": "Stainless Steel" },
      "max_results_per_merchant": 2
    }
  },
  "id": "req_001"
}

Why the path is shorter

Bound uncertainty before execution.

Constraint	Root cause	Resolution
Context inflation	90%+ unusable HTML	Flat, schema-validated JSON
Stale-state cascade	Inventory changes mid-flow	Edge TTL verification
Polling overhead	Sequential multi-site scraping	Consolidated comparison index
Brittle checkout	Dynamic UI variation	UCP / ACP execution payload

Performance figures on this page are design targets from the product requirements.