Run the full demo first
The demo starts the hub, MySQL, a demo business app, one route, one integration client, and a demo tool provider. It is the fastest way to understand the runtime path before connecting your own system.
$ docker compose up --build Console: http://localhost:18900/console/ Login: admin / bailing-demo-admin Route: demo_support
Fresh Ubuntu/Debian servers can use the one-line installer: curl -fsSL https://www.bailinghub.com/install.sh | sh. Use BAILING_INSTALL_MODE=image for official prebuilt images.
Five objects to understand
Route
A business scenario. It selects the target model/executor, memory, knowledge, tools, budget, and delivery policy.
Client
A business system credential. It controls authentication, route allowlists, rate limits, and budget constraints.
Target
The execution backend selected by a route, such as the built-in OpenAI-compatible LLM target or a remote executor.
Tool Provider
A business system endpoint that publishes selected APIs as AI-callable tools through OpenAPI or SDK-generated specs.
Runtime Ledger
The hub-owned state database for jobs, messages, trace events, audit records, approvals, and delivery attempts.
Business Authority
Bailing AI controls tool reach. Your backend remains the final authority for user permissions and business data access.
Recommended reading order
1. Docker Demo
Run the full loop: business system exposes tools, AI calls them, trace and audit records are created.
2. API Contract
Learn how your system triggers jobs, polls status, receives callbacks, and verifies signatures.
3. Business Tools
Expose selected business actions with scopes, risk levels, approval intent, and HMAC-signed tool calls.
4. SDK
Use PHP, Node, Python, or the plain HTTP/OpenAPI contract from any language.