Merchant integration

Challenger

Generated from this merchant’s live profile. Every identifier and example below is real for this deployment.

Identity

Merchant IDchallenger

Agent IDmerchant_challenger_5MW9D

Platformcustom / custom

CurrencySGD

Categorylaptops

Agent networkenabled — receives customer intents

Storefront agentenabled

Payment acceptanceSimulated Visa Acceptance (no credentials configured)

Integration status

Catalogue sourceseeded mirror

Products indexed6

Order creationnot_configured

Databasein-memory-seed

Sample SKUsCHA-NITRO-V16, CHA-LEGION-PRO-5, CHA-XPS-14

Commercial policy (server-side only)

Primary objectiveaov

Max discount3%

Min margin9%

Bundle allowanceSGD 130

Standard warranty2 years

Approved sales rules2

These values are never returned by a public endpoint and are never sent to a browser. They are applied inside the offer validator before an offer can be sealed.

Endpoints

POST/api/storefront/chat

Merchant-scoped storefront conversation. Tools are bound to this merchantId; there is no cross-merchant search.

POST/api/shopify/sync

Pull catalogue, variants and inventory into the normalized mirror.

POST/api/shopify/order

Create an order for a SKU. Returns shopifyOrderStatus: created | not_configured | failed | demo.

GET/api/public/merchant/challenger

Public browser-safe config for the storefront widget. Agent id only, no secrets.

POST/api/exchange/request

Customer-agent entry point. Signed RFO fans out to every network-enabled merchant agent.

POST/api/exchange/counter

One counteroffer round against a sealed offer, evaluated against this merchant's policy floor.

POST/api/offers/:offerId/lock

Re-check inventory, re-canonicalize, compare SHA-256, freeze the offer.

POST/api/payments/instruction

Create a Payment Instruction bound to this merchant, an amount ceiling and an expiry.

POST/api/payments/authorize

Enforce the instruction controls, then authorize through the Visa Acceptance adapter.

GET/api/events/:sessionId

SSE stream of agent events for a session.

Examples

Storefront chat

curl -X POST http://localhost:3000/api/storefront/chat \
  -H 'content-type: application/json' \
  -d '{
    "merchantId": "challenger",
    "message": "I need something light for coding under SGD 1500",
    "history": []
  }'

Create an order

curl -X POST http://localhost:3000/api/shopify/order \
  -H 'content-type: application/json' \
  -d '{
    "merchantId": "challenger",
    "sku": "CHA-NITRO-V16",
    "quantity": 1,
    "amount": 1599,
    "currency": "SGD",
    "reference": "PI-EXAMPLE"
  }'

Offer response shape (network mode)

{
  "offerId": "ofbiz_a1b2c3d4",
  "requestId": "req_xxxx",
  "merchantId": "challenger",
  "sku": "CHA-NITRO-V16",
  "price": 1551,
  "currency": "SGD",
  "bundle": {
    "type": "mouse",
    "description": "Wireless mouse",
    "value": 35
  },
  "warrantyYears": 2,
  "deliveryDays": 1,
  "availability": "in_stock",
  "merchantPolicyVerified": true,
  "state": "sealed",
  "hash": "sha-256 hex of the canonical offer",
  "expiresAt": "2026-08-29T13:45:00.000Z"
}

Storefront widget

Drop-in embed

<script src="http://localhost:3000/widget.js"
  data-merchant-id="challenger"
  data-agent-id="merchant_challenger_5MW9D"
  async></script>

Auth and security

Public identifiers. The agent id and merchant id are browser-safe and are the only values the widget receives.
Server-side secrets. Commercial rules, cost prices, margins, Shopify tokens, Visa credentials and the agent signing key never leave the server and never enter a model prompt.
Agent request signing. Customer-agent requests carry an Ed25519 signature over an RFC 9421-style signature base with a nonce and timestamp; the merchant agent verifies before constructing an offer. This is a TAP-style implementation against Visa’s public protocol model — the demo key is locally generated and is not registered with Visa.
Merchant isolation. Storefront sessions are constructed with one merchant id and the tools close over it. No cross-merchant read path exists.
Offer integrity. A sealed offer is canonicalized and hashed with SHA-256. Authorization is refused if the hash changes.
This prototype has no merchant authentication. A production deployment would issue per-merchant API keys with HMAC request signing and scope every endpoint to the authenticated merchant.