ClutchCall is a real-time platform with five typed modalities: voice, streams, robotics, games, and data. All five modalities use the same MoQT (Media-over-QUIC Transport) relay mesh. Native, hermetically-built SDKs ship for TypeScript, Python, Go, Rust, Java, and .NET. A Unity UPM transport package also ships. All bindings share one C++23 core. The core emits the same wire envelope in every language. Because of this, a Python publisher, a browser subscriber, and a Unity client interoperate without translation.

​
What’s in this site

Modalities

The five-modality model: voice, streams, robotics, games, and data. This page tells you when to use each modality.

Quickstart

Build a working app in less than five minutes. Pick a modality and follow the steps.

SDK Reference

A reference for each language. It covers every modality and every method, with end-to-end examples.

Architecture

QUIC, WebTransport, MoQT, the C++ core, and the relay mesh.

​
Start here for a common task

The four things people build first, each a complete worked example.

Embed an agent widget on your website

One tag plus one backend route puts a voice, text, and video agent on any page. The media runs on MoQT over QUIC, and no credential ships to the browser.

Run your LiveKit agent on our transport

Install a plugin into your existing livekit-agents worker. Your agent code, plugins, and provider keys do not change — only the bytes on the wire. There is no LiveKit server.

Make an outbound call

Dial one number or hand over a list and let the engine pace the campaign. The same worker answers, inbound or outbound.

Fetch call recordings through the API

List recordings with filters and stats, mint a one-hour presigned download URL, or get pushed a webhook the moment one lands.

​
Modalities at a glance

The platform also has these surfaces:

​
One substrate

The same call can flow through any combination of runtimes:
All runtimes speak MoQT directly. The relay routes by capability. A capability is an open-ended intent string, for example voice/opus, game.state, or ros.reliable. A track can reach any consumer that registered for that capability. The publisher does not need to know that the consumers exist.

​
Polyglot, but one substrate

All SDKs are built hermetically. They share the same C++ core, the same wire envelope, and the same modality conventions. Cross-language calls work without extra steps.