Money

Gatewayone auth, scope and meter plane

Dispatch

Dispatchroutes each call to the right providerBridgepreviewbridges a stream between transportsInterchangepreviewconverts between media formats

Studio

Clipscut and publish clipsEditorpreviewedit in the browserCollabpreviewmulti-user editing sessionsPodcastpreviewrecord and publish podcastsStudio AIpreviewAI-assisted production

Infrastructure

Pulsepreviewlive stream analyticsCodecpreviewcodec benchmarksMetricspreviewthe metrics sinkEmailpreviewthe email edgeGPUpreviewGPU seconds at the edge

Transports

Realtimepreviewthe realtime protocol planeMoQpreviewMedia over QUIC ingest and deliveryNDIpreviewNDI over the public internetDantepreviewDante audio across networksOMTpreviewOpen Media Transport streamsSRTpreviewSRT ingest and relay

Intelligence

Voicepreviewsynthetic and cloned voiceCaptionspreviewlive and file captionsChapterspreviewautomatic chapter markersTranscribepreviewspeech to textSentimentpreviewsentiment across a transcriptSearchpreviewsearch inside the mediaEnhancepreviewclean up audio and videoAcuitypreviewmedia quality analysis

Media

Media Enginepreviewthe Media Engine overview

Deliver

Listenaudio-only deliveryCrestpreviewcamera and board mix to a tabBadgepreviewembeddable live badge

Media

ClipsListenPulsepreviewRealtimepreviewMoQpreviewNDIpreviewDantepreviewOMTpreviewSRTpreviewVoicepreviewCaptionspreviewChapterspreviewEditorpreviewCollabpreviewPodcastpreviewStudio AIpreviewTranscribepreviewSentimentpreviewSearchpreviewMedia EnginepreviewCodecpreviewEnhancepreviewMetricspreviewEmailpreviewCrestpreviewAcuitypreviewBadgepreviewGPUpreview

Money

Gateway

Dispatch

DispatchBridgepreviewInterchangepreview

Company

PricingDocsSign in

Introduction

WAVE is an open protocol and one API for video — built so people and autonomous agents use the same rails. You integrate once; every WAVE capability is callable by you through the SDK and payable by an agent over HTTP-402 (x402).

Video infrastructure has historically assumed a person stays in the loop: an account is created, a card is stored, a key is issued, and access is gated by that credential from then on. That works while someone is present to provision and authorize. It breaks when the caller is an autonomous system that has to find a capability, learn its price, pay, and act — with nobody there to fill in a form.

WAVE's answer is not a second product for agents. It is one surface where payment, identity, and metering are part of the protocol rather than a side channel.

Three engines, one surface

The hard problems are solved once, each at the plane where it belongs.

  • Media Engine — carry the signal. Clock, integrity, A/V sync, reliability, and metering live in the engine, so every transport is a thin adapter over a shared core. The protocol is a parameter you pass at call time, not a commitment you make at design time.
  • Money Engine — clear the payment. Verification, settlement, identity, and compliance screening are handled once. People pay with cards and keys; agents settle over HTTP-402. Same rail, same enforcement.
  • Dispatch Engine — choose the path. Each unit of work is classified at the edge and routed to the cheapest capable path, metered per decision. Your keys, prompts, and inference stay on your infrastructure — the edge returns a decision, not a completion.

These are three planes of one contract, not three products that share a login. An agent transacts on all three the same way.

The shape of the platform

  • One API. Clips, voice, captions, transcription, search, and more — a single typed contract.
  • One gateway. Authentication, scope, entitlement, and metering are enforced at one edge. Policy is written once instead of drifting per product.
  • Agent-native. Agents discover, negotiate, and pay for access over x402 and the Machine Payments Protocol (MPP) — no human in the loop.
Agent commerce isn't a product on WAVE — it's how the whole platform works. Every capability is agent-payable.

Where to go next