BailingHubAGENT-TO-BUSINESS
中文GitHubTry online
CONNECT

Decide who plans and where identity comes from,then choose an integration path

The same platform name can hide very different runtime modes. BailingHub separates five paths by workplace, orchestration, and trusted identity.

Choose an entry pathOpen integration docs
Five integration pathsIdentity model shown per pathInstallation and setup guides
01FIVE INTEGRATION PATHS

Connect the layer you actually need

Compare orchestration, identity, and setup requirements to choose the right connection for your system.

WEB ASSISTANT01
Core

Work inside the existing back office

Embed the official assistant so users can query and operate from familiar pages.

Read the setup guide↗
Goal
Add natural-language operations to commerce, SaaS, CRM, or ERP without rebuilding it.
Orchestration
BailingHub handles conversation, routing, and tool orchestration centrally.
Identity
The business system issues a short-lived trusted ticket from the current login.
Setup notes
SDK and ticket integration are required; the backend remains final authority.
AGENT CLIENT02
v0.7.0 · released

Let a local agent operate the business

Select commerce and inventory authorizations, then check stock, change a price, and publish under existing rules.

SDK v0.7.0 integration and upgrade↗DSH adapter v0.7.0↗
Goal
Query, update, and run permitted capabilities from a desktop or local agent.
Orchestration
The local agent plans; BailingHub supplies rules, capabilities, approval, and audit.
Identity
Authorize accounts separately, then select systems within the same Hub and audit domain.
Setup notes
The host integrates browser authorization, tool calls, and original-request recovery under existing business permissions.
API · MCP · AUTOMATION03
Multi-platform

Connect existing agents and automation

Start governed tasks from custom apps, Dify, n8n, an MCP host, or an agent skill.

Read Client API docs↗MCP Server↗
Goal
Reuse existing flows while keeping unified jobs, approvals, and audit.
Orchestration
The caller submits an objective; BailingHub manages routing and job lifecycle centrally.
Identity
Usually a route-scoped Client Token managed by the operator.
Setup notes
MCP here is Client Token job mode; Agent Session belongs under Agent Client.
EXECUTOR04
Runtime

Run Hub jobs locally or inside a private network

Handle code review, local files, private-network work, and specialized tools.

OpenClaw Executor↗
Goal
Connect a dedicated runtime without exposing a public inbound port.
Orchestration
BailingHub dispatches a Job; the executor claims, heartbeats, runs, and reports it.
Identity
A target-scoped Executor Token over an outbound connection.
Setup notes
An executor is not an interactive Agent Client and does not inherit a user login.
BUSINESS ADAPTERS05
Adapter-specific

Expose capabilities from an existing system

Use business SDKs, packaged adapters, or reference recipes for declaration and execution.

CRMEB adapter v2.4.1↗Business SDKs↗
Goal
Reduce repeated integration work across commerce, SaaS, CRM, and ERP systems.
Orchestration
The Hub governs calls and the adapter executes under backend authority; the chosen entry point handles planning.
Identity
Reuse the source system user, tenant, role, and permission model.
Setup notes
CRMEB is publicly listed; RuoYi and JeecgBoot are community reference recipes.
02ECOSYSTEM INTEGRATIONS

Choose a component and make your first call

Find components, platform plugins, and integration recipes, then follow the setup instructions to make your first call.

01 · WEB ASSISTANTView path↗

Public Core capability

BailingHub embedded assistant

Included in Core v0.9.0
Orchestration
BailingHub centrally handles conversation, routing, and tools.
Identity & auth
The business system issues a short-lived trusted ticket from the active login.
Version / status
BailingHub Core v0.9.0
Getting started
Integrate the business SDK and ticket → embed the assistant → complete one read and one permitted write → compare the native record with the trace.
Setup guide↗

02 · AGENT CLIENTView path↗

Independent local-agent adapter

DeepSeek Harness Agent Client

v0.7.0 available to install
Orchestration
The local DSH agent plans; BailingHub keeps authorization-specific execution and links synchronized text to original traces.
Identity & auth
Browser authorization, PKCE, and a revocable Agent Session; no Client Token.
Version / status
dsh-bailinghub v0.7.0 · SDK v0.7.0 · Core v0.9.0
Getting started
Authorize commerce and inventory → select both before the first message → check stock, then reprice and publish if available → inspect completed, awaiting-approval, and failed calls.
Account and conversation guide↗Plugin v0.7.0↗SDK v0.7.0 integration and upgrade↗

03 · API · MCP · AUTOMATIONView path↗

Workflow / agent tool plugin

Dify Marketplace plugin

Available in Dify Marketplace · 0.1.2
Orchestration
Dify submits an objective; BailingHub centrally owns the governed job lifecycle.
Identity & auth
A dedicated route-scoped Client Token stored in Dify credentials.
Version / status
Plugin 0.1.2 · Marketplace installable
Getting started
Install from Marketplace → set Hub URL and dedicated token → submit_governed_job → wait_for_job → reach a terminal state under one job_id.
Dify Marketplace↗Plugin source↗
Automation workflow node

n8n community node

Verified Community Node and searchable in n8n Cloud
Orchestration
n8n composes the workflow; BailingHub governs each business job.
Identity & auth
A dedicated Client Token stored in an n8n credential; no Hub-admin or business credential.
Version / status
n8n-nodes-bailinghub 0.1.1 · available in Cloud
Getting started
Add the node and credential → connect Submit Governed Job to Wait for Job → verify that waiting polls the original job_id only.
npm package↗Node source↗
Portable Agent Skill

SkillHub Agent Skill

Publicly listed on SkillHub
Orchestration
The agent workspace submits a task; BailingHub centrally plans and governs the rest.
Identity & auth
The operator fixes Hub URL, one route, and a route-scoped Client Token outside the model.
Version / status
bailinghub-governed-actions 0.1.1
Getting started
Install the Skill → set URL, route, and token in secret configuration → run a no-side-effect task → submit, inspect, or wait on the same job_id.
SkillHub listing↗
Portable Agent Skill

Qoder / QoderWork Skill

Available in Qoder Marketplace · QoderWork compatibility unverified
Orchestration
The Qoder workspace submits a task; BailingHub owns routing, execution, and terminal state.
Identity & auth
The operator fixes Hub URL, route, and Client Token in secure configuration, never in chat.
Version / status
BailingHub Governed Actions 0.1.1 · public listing
Getting started
Install from the public page → inject the three deployment values securely → run a no-side-effect task → inspect job_id and terminal state.
Qoder Marketplace↗
stdio MCP compatibility entry

BailingHub MCP Server

v0.7.0 public package; Registry listings are maintained separately
Orchestration
The MCP host submits an objective; BailingHub centrally orchestrates the job.
Identity & auth
Process configuration fixes Hub URL, one route, and a route-scoped Client Token.
Version / status
bailinghub-mcp-server v0.7.0
Getting started
Start the 0.7.0 stdio server → set a dedicated token and fixed route → submit and bounded-wait on one job → query again after timeout instead of resubmitting.
MCP Server v0.7.0↗npm package↗

04 · EXECUTORView path↗

Outbound executor

OpenClaw Executor Skill

Publicly searchable and installable on ClawHub
Orchestration
BailingHub creates and dispatches the Job; OpenClaw claims, heartbeats, executes, and returns the result.
Identity & auth
A target-scoped Executor Token, never an end-user business login.
Version / status
Public ClawHub listing · independently versioned
Getting started
Install from ClawHub → configure only the Executor Token → observe heartbeat → claim a test Job → return a verifiable result under the same Job ID.
ClawHub listing↗

05 · BUSINESS ADAPTERSView path↗

Independent business adapter

BailingHub for CRMEB

Available in the CRMEB marketplace
Orchestration
The Hub governs calls; the plugin uses native CRMEB services for permission checks and business operations.
Identity & auth
The active CRMEB administrator, role, and native permissions.
Version / status
Adapter 2.4.1 · validated on CRMEB-KY v6
Getting started
Install → configure the Hub connection in CRMEB and register the tool provider in BailingHub → run a permitted action as a normal admin → compare the native CRMEB record with the trace.
CRMEB marketplace↗Adapter v2.4.1↗
Community integration recipe

RuoYi-Vue-Pro

Community integration reference
Orchestration
BailingHub governs the action; a thin adapter reuses the existing after-sales service, tenant context, and permissions.
Identity & auth
The source login, tenant context, and trade:after-sale:* permissions.
Version / status
Integration reference · adapt to your business-system version
Getting started
Implement one after-sale read and refund write → prove the read → then verify approval, argument snapshot, idempotency, and the native record.
English recipe↗
Community integration recipe

JeecgBoot

Community integration reference
Orchestration
BailingHub governs the action; a thin adapter invokes the original JeecgBoot user service.
Identity & auth
TenantContext, original Shiro permission, and operator/target tenant membership.
Version / status
Integration reference · adapt to your business-system version
Getting started
Implement user read and freeze/unfreeze → prove native permission denial still works → match approval, idempotency, native record, and trace.
English recipe↗
03RUNTIME COMPARISON

How the components work together

Compare where planning runs and how identity is established to choose the components for your integration.

01Agent Client

Local planning

A local agent receives projected capabilities and plans.

02Client API / MCP

Central planning

The caller submits an objective and the Hub owns the job lifecycle.

03Executor

Job runtime

Claims a Hub-created Job and does not represent a signed-in business user.

04Business adapter

Final execution

Runs inside the source system under its existing permission model.

Not sure which path fits? Start from where the user works

A business console, local agent, automation flow, and private runtime each map to a different integration path.

Explore use casesOpen integration docs