Developer Docs

Build something your assistant can do, or write an app that talks to it.

A skill runs on the hub and answers a particular request. An SDK is a library your app uses to send requests to the hub. Choose the path that fits what you want to make.

Start Here

Build Your First SkillMake Pocket Quiz, a small game that speaks English and French. See it work at each step.

SDKsChoose a language and make the first request.

Writing a SkillLook up skill helpers, conversation rules, tests, and packaging checks.

MCP ServerConnect Claude, Codex, Cursor, and remote agents.

MQTTBroker credentials, TLS, topics, and SDK usage.

SDK FunctionsControl plane, identity, runtime, and helper calls.

Provision HubsDiscover skills, then create hubs and runtime groups from code.

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.

Build A Skill

Start with the Pocket Quiz tutorial. You can write it and test it on your computer before you have a hub. The tutorial explains what each file does and shows the result to expect.

When it passes its checks, follow Add Your Own Skill to install it on a test hub. Ask its first question aloud, try a follow-up, and check that Stop ends the game.

Basic Flow

These steps are for an app that connects to a hub. Thalovant creates the client identity and access rules; your SDK uses that identity to connect directly to the hub.

1. Choose a hub. Start with a public hub when you are testing.
2. Create a client identity. Authenticated API actions require API access on the workspace.
3. Install an SDK. Pick the language used by your app, service, or agent.
4. Connect over WSS first. WSS is the default public transport.
5. Check transport support. Python, Node.js, Go, and Rust also support HTTPS and MQTT when enabled on the hub. Kotlin, Swift, and .NET use WSS; embedded C needs your application’s transport.
6. Request an SDK Origin for browser apps. Customer-owned browser domains need review before cross-origin API calls work.
7. Add context. Send user, device, session, and trace metadata after the first request works.

SDKs

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.

KotlinJVM services and Android clients.

SwiftApple apps and compatible Linux clients.

.NETC# services, desktop apps, and Unity clients.

Embedded CFirmware with application-owned transport and storage.

Reference

Sessions and ContextUsers, devices, flows, and traces.

Events and OutputText, speech, display items, and event streams.

What Can My Hub Be Asked?List intents and their sentences over the client's own session.

ActionsButtons, scans, codes, and structured commands.

SDK ContractWhat every SDK should expose.

v3 Noise HandshakeThe only transport handshake a hub accepts.