BEEOS CLOUD / DEVELOPER REFERENCE
Choose an SDK
Select the Cloud SDK boundary that owns your operation
| You are building | SDK / source class | Auth and responsibility |
|---|---|---|
| Product backend | Server SDK: BeeOSClient (TypeScript/Python), NewBeeOSClient (Go) | bsk_; typed resource methods and results (2.0.0) |
| OpenClaw, Hermes, or custom agent | Harness SDK. Python BeeOSAgentRuntime; TypeScript RuntimeRegistrationCoordinator | Runtime token; registration, inbound chat, and method handlers |
| Web or mobile product app | Product frontend integration; no separate Cloud client SDK | Product-owned authentication and events; backend-issued, purpose-scoped data descriptors |
The Server SDK has TypeScript, Python, and Go. The Harness SDK has TypeScript and Python. There is no Java, Rust, or Go Harness package. Follow the language matrix and each SDK reference for exact signatures.
Use the Cloud package and class for the backend or agent role you are implementing. The product frontend uses its own app stack: it sends business requests to its backend, consumes the backend's user event channel, and connects to data endpoints only with authorized descriptors. Server keys, runtime tokens, product sessions, and descriptors cannot be exchanged between roles.
For a first complete flow, use a backend to create or find an instance, locate an agent, create a conversation, and send a message. Quickstart shows the available source calls.