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”SDKsChoose a language and make the first request.
MCP ServerConnect Claude, Codex, Cursor, and remote agents.
MQTTBroker credentials, TLS, topics, and SDK usage.
SDK FunctionsControl plane, identity, runtime, and helper calls.
OperationsPoll accepted commands through commit, apply, readiness, or failure.
Status StreamResume ordered condition events from a durable cursor.
GitOps CommandsRender, accept, and follow an idempotent Git reconciliation.
Hub EndpointsWSS, HTTPS, and MQTT over TLS.
Identity FilesCredentials, endpoints, and broker settings.
SDK OriginsReviewed browser domains for cross-origin SDK calls.
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.
- Request an SDK Origin for browser apps. Customer-owned browser domains need review before cross-origin API calls work.
- Add context. Send user, device, session, and trace metadata after the first request works.
PythonAgents, tools, services, notebooks, and tests.
Node.jsBackends, scripts, bots, and TypeScript agents.
GoServices, gateways, CLIs, and small agents.
RustStrict clients, embedded work, and reliable services.
Reference
Section titled “Reference”Sessions and ContextUsers, devices, flows, and traces.
Events and OutputText, speech, display items, and event streams.
ActionsButtons, scans, codes, and structured commands.
SDK ContractWhat every SDK should expose.