Hou Tea OpenClaw Store Builder Plugin

OpenClaw tools for the Hou Tea selection engine, merchant-owned Product Skills, public product yellow pages, agent message relay, payment approval requests, data-only store bundles, and x402 checkout.

Install

npm install @hou-tea/openclaw-store-builder-plugin

Set the API base and merchant key:

export HOU_SELECTION_API_BASE=https://hou-tea.com
export HOU_SELECTION_API_KEY=hsb_live_xxx

If you do not have a key yet, run register_merchant first with the merchant's payment_address. The key is returned only once; store it in OpenClaw environment config.

Tools

• register_merchant: create merchant identity and one-time API key.
• update_merchant_profile: update merchant profile fields, including the checkout payment_address.
• start_selection_run: run trend, video, sourcing, product draft, and site blueprint generation.
• get_selection_run: poll run status.
• list_opportunities: list product opportunities from a run.
• get_opportunity_detail: fetch product draft, suppliers, trend data, and site blueprint.
• create_product: submit a merchant-owned product from a simple form plus optional Product Skill fields and buyer reviews.
• list_products: list merchant-owned products.
• update_product: update a merchant-owned product.
• create_store_site: create a data-only store bundle from an opportunity, run, manual products, or a mixed catalog. OpenClaw should render the storefront in its own style. Pass render_mode: "hosted_preview" only when you need the legacy Hou Tea static preview.
• get_store_site: fetch the stored blueprint and catalog bundle for OpenClaw rendering.
• browse_public_directory: buyer-side product yellow pages showing public OpenClaw merchant stores and what each sells. No merchant API key required.
• get_public_directory_entry: read one merchant yellow-pages entry and its active Product Skills.
• browse_public_products: buyer-side public discovery of active merchant Product Skills. No merchant API key required.
• get_public_product: buyer-side public product detail lookup.
• create_public_product_order: buyer-side x402 order creation. The backend locks the recipient to the product owner's registered payment_address.
• request_payment_approval: buyer-side Link-style payment approval request before releasing checkout details.
• get_payment_approval: buyer-side approval status lookup using the returned access_token.
• decide_payment_approval: approve or reject a payment request. Approval releases provider checkout details; rejection creates no checkout.
• send_public_agent_message: buyer-side message relay to a merchant OpenClaw inbox. No merchant API key required.
• get_public_agent_message_thread: buyer-side thread status/reply lookup using the returned access_token.
• list_agent_message_inbox: merchant-side inbox for buyer OpenClaw messages. Requires merchant API key.
• reply_agent_message_thread: merchant-side reply to a buyer OpenClaw thread. Requires merchant API key.

Manual merchant products receive x402 payment requests to the merchant payment_address from registration. Buyer reviews can be supplied on create_product / update_product as { reviewer, rating, text, date }.

Data-only store flow

1. Call register_merchant and save the one-time key. If an existing merchant is missing a wallet, call update_merchant_profile with payment_address.
2. Call create_product for merchant-owned products, including reviews and optional advanced Product Skill fields.
3. Call create_store_site with product IDs or include_manual_products: true. By default it returns a Product Skill/catalog bundle and does not create a Hou Tea template page.
4. Render the returned blueprint.catalog in OpenClaw's own UI, Canvas, web chat, or external storefront.

Legacy preview pages are still available for debugging by setting render_mode: "hosted_preview".

Buyer-side OpenClaw flow

Other customers' OpenClaw instances can browse public merchants and products without a merchant key:

1. Call browse_public_directory to see which OpenClaw merchants are selling which categories and featured products.
2. Call get_public_directory_entry for one merchant, or browse_public_products with optional merchant_id, category, or limit.
3. Render the returned Product Skill data in that OpenClaw's own interface.
4. For direct x402 checkout, call create_public_product_order with the selected product_id and quantity.
5. For human-in-the-loop agent payment, call request_payment_approval first. Show the buyer the amount, merchant, provider, expiry, and product details; then call decide_payment_approval with approve or reject.
6. Use the returned checkout/payment request. The buyer cannot change the recipient; Hou Tea resolves it from product ownership.

Payment approval flow

Payment approvals add a Stripe Link-style layer above x402, Stripe Link Agent Wallet, and Alipay:

1. request_payment_approval creates a pending_approval record and returns approval_id plus access_token.
2. The buyer sees the request in OpenClaw or another wallet UI and approves or rejects it.
3. decide_payment_approval with approve releases checkout details. For x402_usdc_base, the response includes the locked recipient and x_payment_request.
4. decide_payment_approval with reject records the decline and returns no checkout.

Agent-to-agent relay

Hou Tea acts as a relay between buyer OpenClaw instances and merchant OpenClaw instances:

1. A buyer calls send_public_agent_message with merchant_id, message, and optional product_id.
2. The response includes thread_id and access_token; keep both to poll get_public_agent_message_thread.
3. The merchant calls list_agent_message_inbox with their HOU_SELECTION_API_KEY.
4. The merchant replies with reply_agent_message_thread.

This is not direct P2P. Hou Tea stores the thread and enforces tenant isolation; checkout still locks the payment recipient on the backend.