1. Install
npm
clutchcall_core_ffi.{so,dylib,dll}. See each per-language installation
page.
2. Get a token
Every modality authenticates with a tenant token. The relay checks the token through its namespace-auth hook. The control-plane API key (tRPC,CLUTCHCALL_CREDENTIALS) mints data-plane tokens. Each token is
scoped to the namespaces that the client needs.
3. Pick a modality
What just happened
- The SDK opened a QUIC link to
relay.clutchcall.dev:443over MoQT. In the browser, the SDK used WebTransport. The tenant token authorized the session. - For control-plane modality methods (
v.calls.originate,streams.liveInputs.create, etc.), the SDK called tRPC procedures on the control-plane API over HTTP/3. - For data-plane methods (
subscribeState,publishInput, etc.), the SDK opened MoQT publish / subscribe requests. The relay fans these out to every matching subscriber.
Next steps
Modalities overview
The five-modality model and when to pick each modality.
Architecture
The MoQT relay mesh, the C++ core, and how the modality layer fits.
Authentication
API keys, relay tokens, namespace-auth, and JWT signing.
SDK Reference
A reference for every modality, every method, and every language.

