The Web Audio Video Engine
WAVE started as the Web Audio Video Engine. The “AV” keeps growing up — here is everything it means now, and how you put each one to work.
Origin: Web Audio Video Engine — one engine for getting audio and video where it needs to go.
Four letters, many meanings
Everything the AV stands for
Audio · Video
LiveThe literal one: every AV transport behind a single API.
NDI, SRT, RIST, Dante, SMPTE ST 2110, MoQ, WebRTC, RTMP, HLS — spoken through one contract instead of nine integrations.
Agentic Video
LiveVideo that an autonomous agent can act on — discover, request, pay, receive — with no human in the loop.
Native HTTP-402 (x402) payment negotiation and the Metered Payment Protocol let agents transact for media under your governance.
Agent Video
LiveVideo built for machines as first-class citizens, not just people.
Every capability is published in a machine-readable manifest and is individually metered and payable — discoverable by agents and humans alike.
Audio-Video Verification
BuildingProving you got what was sent — provenance and integrity across the hop.
The WAVE Media Engine stamps each unit with sequence, media-time, and a content fingerprint, so a receiver can verify integrity end-to-end.
Agent Video Engineering
LiveThe platform you build on — SDKs, MCP, and a CLI for shipping video features fast.
TypeScript and Python SDKs, a developer portal, and an open contract — for the engineers (human or agent) wiring video into their product.
Anything → Video
BuildingAn open-core substrate any protocol can plug into.
The WAVE Media Engine is an Apache-2.0 core that handles clock, integrity, sync, reliability, and metering once — each transport is a thin adapter on top.
One name, many jobs
Whatever the “AV” stands for this year, the promise is the same: audio and video that arrive intact, on time, and ready for whoever — or whatever — is on the other end.