Skip to main content

Real-Time Voice Bridge Protocol

The typed bridge between a live call and your application.

Keep telephony in the voice platform. Give an AI agent, IVR, or audio service a small, transport-independent contract for control and duplex media.

Try it outLearn the model
  • 3released SDKs
  • 48frozen wire fixtures
  • 1 specgenerates every contract
Owns the callVoice peerTelephony
Owns the logicApplication peerAgent · IVR · service
Current profilesrtvbp.v1rtvbp.webrtc.v1

Start here

Build from your boundary.​

Choose an SDK when you want a complete runtime, or the wire path when RTVBP meets another stack.

TS

TypeScript SDK

One generated API for Node 22+ and evergreen browsers, including native WebRTC.

@babelforce/rtvbp · 0.1.0Open quickstart GO

Go SDK

Build either protocol role with typed peers, WebSocket audio, or Pion WebRTC.

Go module · 0.1.1Open quickstart RS

Rust SDK

Use the same generated contracts through Tokio, WebSocket, and WebRTC runtimes.

Rust crate source · 0.1.0Open quickstart {}

Wire protocol

Implement a peer directly from generated envelopes, roles, flows, and vectors.

Protocol snapshot · 1.0.0Open quickstart

Understand

A small model with hard guarantees.​

The payload is invariant; transport and envelope are negotiated choices. Generated proof keeps them aligned.

01

Core concepts

Roles, messages, media, and the three independent layers.

02

Profiles

How peers negotiate a compatible transport, envelope, and catalog.

03

Transport bindings

Choose WebSocket audio or WebRTC media without changing payloads.