Run the first business action in 10 minutes
The public Docker Demo needs neither a production business system nor a model key. It uses a deterministic demo agent, while tool allowlists, trusted subjects, signatures, writes, approvals, and traces all use the real runtime path.
- Start BailingHub, MySQL, and Demo Business.
- Submit one job that reads an order and creates a support ticket.
- Inspect capability discovery, tool calls, and results under the same
job_id. - Submit a refund request and approve or deny its intent in Demo Business.
1. Start the demo
Section titled “1. Start the demo”export BAILING_TOKEN="${BAILING_TOKEN:-$(openssl rand -hex 32)}"docker compose up --buildOn a fresh Ubuntu/Debian host, you can use the public installer:
curl -fsSL https://www.bailinghub.com/install.sh | shThen open:
- Console:
http://localhost:18900/console/ - Demo Business:
http://localhost:19080/ - Health:
http://localhost:18900/health
2. Submit the first job
Section titled “2. Submit the first job”curl -sS http://localhost:18900/run \ -H 'content-type: application/json' \ -H 'authorization: Bearer bailing-demo-client-token' \ -d '{ "request_id": "quickstart-001", "route": "demo_support", "input": "Read order SO-1001 and create a support ticket for manual follow-up", "metadata": { "visitor_uid": "visitor-001", "operator_uid": "demo-user-001" } }'Poll the returned job_id with the same client token:
curl -sS http://localhost:18900/jobs/<job_id> \ -H 'authorization: Bearer bailing-demo-client-token'3. Inspect the evidence
Section titled “3. Inspect the evidence”In the console, confirm that the route exposed only its allowed demo tools, the business call carried a trusted subject, the read and write each produced tool trace events, and the visible result entered the same ledger.
4. Verify approval
Section titled “4. Verify approval”Use a new request_id and ask for a refund on SO-1001. The job should pause and deliver an approval intent to Demo Business. Approval or denial applies only to the frozen call whose args_hash matches.