English Français العربية

Hive Openclaw Bridge

السجل الرسمي المالية والمدفوعات

Reference integration with @kinthaiofficial OpenClaw 3-layer payment governance

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http hive-openclaw-bridge 'https://hive-mcp-gateway.onrender.com/openclaw-bridge/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "hive-openclaw-bridge": {
            "type": "http",
            "url": "https://hive-mcp-gateway.onrender.com/openclaw-bridge/mcp"
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. hive-mcp-openclaw-bridge
  2. Why this exists
  3. Background reading
  4. Tools
  5. Doors
  6. Lifecycle of a paid call
  7. Quickstart
  8. Configuration
  9. Related
  10. License
  11. Hive Civilization Directory

hive-mcp-openclaw-bridge

Reference integration with @kinthaiofficial's OpenClaw 3-layer payment governance framework. MCP server that wraps Hive Gamification's 8 BOGO doors behind a 4-level hierarchical budget — atomic reserve, upstream POST, settle/release. Real rails. No mock settlement.

Brand: Hive Civilization gold #C08D23 (Pantone 1245 C). License: MIT.

Why this exists

OpenClaw's three-layer model splits payment governance into three concerns:

LayerConcernWhere it lives
Layer 1Internal hierarchical budget — atomic reserve / settlethis server
Layer 2Inter-agent millicent ledger settled at epoch boundariesOpenClaw
Layer 3External x402 settlement on real railsHive Gamification

This bridge demonstrates the Layer 1 ↔ Layer 3 seam. Every paid call to a Hive door (computational-debt, protocol-consensus-tax, pheromone-priority, zk-compliance-shield, capability-leasing, guild-synergy, audit-trail-premium, bounty-routing) is gated by an atomic reservation against every level in the caller's scope path:

Namespace → User → Agent → Task

The most-restrictive level governs. If any level is short of headroom, the upstream HTTP request is never made and no x402 settlement is signed.

The same BudgetHook interface is exposed from @hivemorph/qvac-client v0.2 — drop your own implementation in to wire this hierarchy into a different runtime.

Background reading

Tools

ToolWhat it does
budget_statusInspect caps, spend, reservations, headroom across all 4 levels
budget_set_capOverride a per-key cap at one level
budget_checkRead-only pre-flight against a proposed amount + scope
doors_listList all 8 BOGO doors with endpoint, price, asset, term
door_economicsFetch live /economics for one door
bogo_claimClaim first-use-free via /v1/bogo/claim
door_subscribeCanonical gated path — atomic reserve → upstream POST → settle/release

Doors

DoorEndpointPriceTerm
computational-debt/v1/debt/subscribe0.50 USDC30d
protocol-consensus-tax/v1/pct/subscribe0.25 USDC1 read
pheromone-priority/v1/pheromone/subscribe5.00 USDC30d
zk-compliance-shield/v1/compliance/subscribe1.00 USDC30d
capability-leasing/v1/lease/start0.15 USDC1h
guild-synergy/v1/guild_synergy/subscribe10.00 USDC30d
audit-trail-premium/v1/audit_premium/subscribe3.00 USDC30d
bounty-routing/v1/bounty_routing/route0.50 USDC1 routing

Backend: https://hive-gamification.onrender.com. All endpoints are live and verified.

Lifecycle of a paid call

client → tools/call door_subscribe { door_id, did, scope }
       → atomicReserve(scope, price, asset)
           ├─ each level checked: namespace, user, agent, task
           ├─ headroom = cap − spent − reserved
           └─ short on any level? reject before signing
       → POST hive-gamification.onrender.com<endpoint>
       → 2xx? settle(reservationId)
         non-2xx or throw? release(reservationId)
       → return { ok, reservationId, binding_level, upstream }

Quickstart

git clone https://github.com/srotzin/hive-mcp-openclaw-bridge
cd hive-mcp-openclaw-bridge
npm install
npm start

Then from any MCP client:

POST http://localhost:3000/mcp
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

Configuration

EnvDefaultMeaning
PORT3000listen port
HIVE_BASEhttps://hive-gamification.onrender.comupstream base URL
HIVE_TIMEOUT_MS15000upstream fetch timeout
NAMESPACE_CAP50default namespace-level cap (USDC)
USER_CAP10default user-level cap
AGENT_CAP2default agent-level cap
TASK_CAP0.50default task-level cap

Per-key caps override defaults via budget_set_cap.

License

MIT — see LICENSE.

Hive Civilization Directory

Part of the Hive Civilization — agent-native financial infrastructure.

Brand: #C08D23

الأسئلة الشائعة

ما هو Hive Openclaw Bridge؟

Reference integration with @kinthaiofficial OpenClaw 3-layer payment governance

كيف أثبّت Hive Openclaw Bridge؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http hive-openclaw-bridge 'https://hive-mcp-gateway.onrender.com/openclaw-bridge/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Hive Openclaw Bridge إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل Hive Openclaw Bridge مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Hive Openclaw Bridge؟

ينشره srotzin. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.