Runtime interfaces (APIs, dashboards, wrappers)
Current interface families
The CLI remains the primary automation surface, but BusDK now also includes current API providers, portals, dashboards, event workers, and external integrations. Because modules already parse inputs, validate, and produce outputs, HTTP providers and browser surfaces can sit around the same module contracts without moving all behavior into one monolith.
bus-api hosts provider modules for auth, billing, books, containers, data, events, LLM proxying, sessions, terminal access, usage, and VM status. bus-portal, bus-portal-auth, bus-portal-ai, bus-portal-accounting, bus-ui, bus-chat, and bus-books provide browser-facing entry points. bus-events and the bus-integration-* workers connect asynchronous work, provider APIs, usage capture, cloud operations, SSH execution, and payment-provider events.
The Git repository and workspace datasets are still important contracts for business-data modules. AI product modules add service runtime, authentication, billing, usage, and deployment surfaces around those contracts rather than replacing them.