Developer Docs
Use this section when code needs to connect to a Thalovant hub.
Thalovant creates the client identity and policy. Your SDK connects directly to the hub.
Start Here
Section titled “Start Here” SDKs Choose a language and make the first request.
MQTT Broker credentials, TLS, topics, and SDK usage.
SDK Functions Control plane, identity, runtime, and helper calls.
Hub Endpoints WSS, HTTPS, and MQTT over TLS.
Identity Files Credentials, endpoints, and broker settings.
Basic Flow
Section titled “Basic Flow”- Choose a hub. Start with a public hub when you are testing.
- Create a client identity. Authenticated API actions require API access on the workspace.
- Install an SDK. Pick the language used by your app, service, or agent.
- Connect over WSS first. WSS is the default public transport.
- Use HTTPS or MQTT only when needed. Enable those protocols on the hub before expecting clients to use them.
- Add context. Send user, device, session, and trace metadata after the first request works.
Python Agents, tools, services, notebooks, and tests.
Node.js Backends, scripts, bots, and TypeScript agents.
Go Services, gateways, CLIs, and small agents.
Rust Strict clients, embedded work, and reliable services.
Reference
Section titled “Reference” Sessions and Context Users, devices, flows, and traces.
Events and Output Text, speech, display items, and event streams.
Actions Buttons, scans, codes, and structured commands.
SDK Contract What every SDK should expose.