WAVE is 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 to put each one to work.
Origin: Web Audio Video Engine. One engine for getting audio and video where they need to go.
Four letters, many meanings
Everything the AV stands for
Audio · Video
LiveThe literal one: every AV transport behind a single API.
SRT, RIST, AES67, OMT, MoQ, WebRTC, RTMP, and HLS today, with NDI, Dante, and SMPTE ST 2110 on the roadmap. One contract instead of a separate integration per protocol.
Agentic Video
LiveVideo an autonomous agent can act on: discover, request, pay, and receive, with no person in the loop.
Native HTTP-402 (x402) payment negotiation and the Machine Payments Protocol (MPP) let agents transact for media under your governance.
Agent Video
LiveVideo built for machines as first-class callers, not only for people.
Every capability is published in a machine-readable manifest, individually metered, and payable, so agents and people discover it the same way.
Audio-Video Verification
BuildingProof that you received what was sent: provenance and integrity across the hop.
The WAVE Media Engine stamps each unit with a sequence number, 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.
TypeScript and Python SDKs, a developer portal, and an open contract for the engineers, person or agent, wiring video into a 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 holds: audio and video that arrive intact, on time, and ready for whoever, or whatever, is on the other end.