Back to Documentation

HZRelay Documentation

Public Docs

Full documentation lives at hzrelay.mecverse.com. This page is an evaluator-facing overview.

What HZRelay Is

HZRelay is the routing layer between your app and every real-time provider. Voice, tokens, and webhooks are normalized to one session model and one SDK — codecs, reconnects, and provider wiring are handled by HZRelay so you can focus on product logic.

Three Problems It Solves

  • Voice streams — Twilio sends mulaw 8kHz, Deepgram wants PCM 16kHz, ElevenLabs returns PCM. HZRelay transcodes and normalizes across providers without touching your code.
  • Token streams — LLM output is SSE. Clients want WebSocket. HZRelay fans out one source to web, mobile, and log sinks simultaneously.
  • Webhook events — Every provider has a different payload shape. HZRelay handles signature verification, normalization, and fan-out once for all sources.

SDK Quickstart

Install the SDK and create a session. HZRelay handles provider connections from there.

npm install @hzrelay/sdk
import { createSession } from '@hzrelay/sdk'

const session = await createSession({
  inbound:  { provider: 'twilio' },
  outbound: { stt: 'deepgram', tts: 'elevenlabs', llm: 'openai' },
})

Swap any provider in config. No codec changes, no reconnect logic, no re-architecture.

Getting Access

  • Review stream types and adapter registry in the full docs.
  • Choose Depth 1 (infra only, wire into your own loop) or Depth 2 (managed agent loop, working in an hour).
  • Contact the Mecverse team to discuss fit, access credentials, and integration scope.