rynbox

The box between your business and the agents

Proactive signal ops with an A2A commerce edge. Agents buy over MCP; rynbox scores intent, catches the one finding worth your attention, and keeps reputation-aware commerce at the edge.

Open ops →Connect an agent
Live[SENSITIVE]/api/mcp

Agent-to-agent, not human-to-cart

Traditional e-commerce assumes a browser and a checkout form. A2A commerce assumes an autonomous agent acting on behalf of a customer — discovering products, evaluating offers, and executing contracts through a machine-readable protocol.

Reputation-aware pricing

Every agent action is scored 0–100 from CRM LTV, declared intent, and behavior. Commercial rules grant PREMIUM, STANDARD, THROTTLED, or REJECTED treatment — with tiered discounts applied in real time.

MCP-native commerce

Buyer agents connect over Streamable HTTP. Discovery is open; subscribe, search, cart, checkout, and refunds require a verified DID per call — no session store, fully stateless.

CRM-aware policy

Layered BASE → CAMPAIGN rules can target segments or individual agent DIDs. Campaign offers are opt-in; agents autonomously engage or ignore based on their subscription profile.

Findings inbox, not a KPI wall

Owners watch agent narrative, findings, and edge activity from one ops home — catalog, campaigns, and governance stay under Commerce on the same deploy.

How it works

From catalog to contract

  1. 01

    Stock the store

    Merchandisers load products and commercial policy through the owner portal. Catalog and rules live in Neon Postgres.

  2. 02

    Agents discover

    Buyer agents read the public agent card and call describe_service to learn capabilities, terms, and the identification scheme.

  3. 03

    Identify & subscribe

    Agents present a DID + signature on every identified call. They register offer preferences via subscribe.

  4. 04

    Transact with tier pricing

    search_products returns yourPrice — tier-adjusted. Cart snapshots that price through checkout and confirm_purchase.

  5. 05

    Oversee in the console

    Every scored request streams to signal ops Home. Owners tune CRM, rules, and campaigns from the same domain.

Try it now

Install the skill and make your first trade

Paste one prompt into Cursor, OpenClaw, or Hermes — the agent installs the skill, wires the MCP gateway, and runs a test purchase. No manual config files required.

1 · Paste into your agent

Copy the prompt for your runtime. The agent clones Skill/ from github.com/Weizhen/Rynbox, installs it, connects MCP, and walks the buyer flow.

Cursor

Install the Rynbox buyer skill from https://github.com/Weizhen/Rynbox/tree/main/Skill into my skills directory as rynbox-buyer. Read SKILL.md, connect to [SENSITIVE]/api/mcp, and use identity did:web:hermes.bot with signature sig::did:web:hermes.bot. Then search compute products, add the cheapest in-stock item to cart, checkout, and confirm the purchase.

OpenClaw

Clone https://github.com/Weizhen/Rynbox and run: openclaw skills install ./Rynbox/Skill

Add the Rynbox MCP gateway to my OpenClaw config (mcp-remote → [SENSITIVE]/api/mcp). Use identity did:web:openclaw.ai and signature sig::did:web:openclaw.ai on every identified tool call. Follow the installed skill to subscribe, search compute, and complete a purchase.

Hermes

Install the buyer skill from https://github.com/Weizhen/Rynbox/tree/main/Skill. Connect to [SENSITIVE]/api/mcp as did:web:hermes.bot (signature sig::did:web:hermes.bot). Follow SKILL.md end-to-end: describe_service → subscribe → search_products (compute) → add_to_cart → checkout → confirm_purchase.

2 · Run the bundled buyer

Defaults to this app on localhost and the Hermes demo identity (did:web:hermes.bot):

node Skill/scripts/buy.mjs \
  --category compute --qty 1 --confirm

3 · Manual install (optional)

Prefer doing it yourself? Copy Skill/ into your agent's skills directory and install the MCP SDK:

git clone https://github.com/Weizhen/Rynbox
# Cursor: ~/.cursor/skills/rynbox-buyer/
# OpenClaw: openclaw skills install ./Rynbox/Skill

npm install @modelcontextprotocol/sdk

4 · Wire MCP directly

Streamable HTTP endpoint and agent card for any MCP host:

Endpoint:  [SENSITIVE]/api/mcp
Discovery: [SENSITIVE]/.well-known/agent-card.json

# stdio-only hosts — bridge with mcp-remote:
{
  "mcpServers": {
    "rynbox": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "[SENSITIVE]/api/mcp"]
    }
  }
}

5 · Identity on every call

Identified tools require did + signature as tool arguments (MVP mock: sig::<did>):

const id = {
  did: "did:web:hermes.bot",
  signature: "sig::did:web:hermes.bot"
};

// Open tool — no identity:
describe_service()

// Identified flow:
subscribe({ ...id, categories: ["compute"] })
search_products({ ...id, category: "compute" })
add_to_cart({ ...id, sku, qty: 1 })
checkout({ ...id, cartId })
confirm_purchase({ ...id, orderId })

Watch scored requests appear in real time on ops Home. Full tool catalog and spec: A2A Spec.

Ready to see it live?

Open the console — findings inbox, connectors, and live edge activity, with A2A commerce tools under Commerce.

Open ops →