WAVE · Blog
The blog that reads itself to you.
Press play on any post and WAVE Voice reads it aloud — one of four narrators, with captions that keep your place. The same post an agent can read, hear, or quote through an API. It's not a blog about WAVE — it's WAVE, running on itself.
Narrated by WAVE VoiceCaptioned + follow-alongAgent-readable
-
The whole venue, one fabricA venue is audio, video, captions, and a dozen operators each on a different system. WAVE puts the Dante audio bridge next to its own video and captions path as one addressable fabric.
-
One link, anywhereGetting Dante audio off the LAN used to mean stacking licenses — a controller here, a virtual soundcard there, a hardware bridge on top. WAVE replaces the stack with discovery, bridge, play.
-
Your Dante network just left the buildingDante audio has been jailed to the LAN for twenty years. WAVE bridges a live Dante or AES67 source to a URL — any browser, anywhere, nothing to install.
-
WAVE Mesh is liveWAVE Mesh — the WAVE-native overlay for reachability — is commercially available. Every WAVE device joins one flat, NAT-regardless mesh under a single identity, routed direct when the net allows and relayed when it doesn't, metered end to end. Here's what's live today, what it costs, and the one honest caveat.
-
WAVE is generally availableWAVE's platform is generally available — one API at the gateway, open-core SDKs, and x402 payments that work for people and agents alike. The product surfaces ride on that same API, rolling out in preview. Here's exactly what's live today, and what's next.
-
Render — code-defined videoRender turns a declarative Scene — HTML, CSS, audio, and captions — into a voiced, captioned, alpha-capable video. The open reference renderer runs locally today; the hosted, agent-callable pipeline is in preview behind the same gateway that meters everything else on WAVE.
-
How this blog is poweredThis blog is the dogfood — every WAVE primitive running on itself. Voice that narrates the words you're reading, an edge that serves them, and a pipeline that keeps the two in sync. Here's the whole stack, end to end.
-
WebRTC and sub-second latencyWebRTC is the transport when latency has to be conversational. WAVE runs its own edge WebRTC SFU on Cloudflare — WHIP in, WHEP out — and exposes it through the same open API as every other transport.
-
One API, every transportMost video stacks pick a transport and build around it. WAVE puts one API in front of all of them and makes each transport a thin adapter, so the protocol is a parameter, not a rewrite.
-
NDI at the edgeNDI carries broadcast-grade video over standard IP networks. WAVE treats it as one transport adapter over the Media Engine — ingest NDI on the LAN, deliver anywhere.
-
How an agent pays for videoAn agent can call WAVE for video and settle the bill itself — per use, over x402, with no account. Here is the exact path the request and the payment take.