We use A2B for Agent-to-Business: agents doing governed work through existing systems. BailingHub is an open-source implementation built on ACC, the open Agent Capability Contract. It routes business events, exposes selected OpenAPI/SDK tools through x-agent-capability, enforces governance and approvals, records audit trails, and sends results back to your business system.
Expose selected actions through OpenAPI or SDK-generated specs. The agent only sees what the route allows.
Apply allowlists, risk levels, rate limits, human approval, HMAC signatures, audit logs, and trace data to every tool call.
Tool calls carry an on-behalf-of subject, but your backend remains the final authority for permissions.
Business system / web widget / inbound channel route: BailingHub route context: messages + memory + knowledge + page context brain: model or executor tools: governed business tools call: signed business API call authority: business backend verifies signature and permissions
BailingHub focuses on controlled business actions, audit trails, traceability, and delivery back to the system that triggered the task.
Routes configure models, memory, knowledge, tools, approvals, and delivery. Agents can act dynamically inside governed boundaries.
MCP is a tool protocol ecosystem. BailingHub is the business-side control plane around tools, identity, risk, and audit.
Keep your backend, database, permission table, and business processes. Add a governed AI control plane next to them.
Use the online console to inspect the console and product model without installing anything. Use Docker Demo when you want the full technical loop on your own machine.