The WAVE Media Engine
One engine gets audio and video anywhere, intact, on time, and metered. We build the hard parts once; every transport is a thin adapter on top.
81 capabilities, 34 priced
Every one is the same call for a person with a key and an agent with a wallet.
Included with a key47 paths answer without a payment step
Each chip opens the machine-readable document for that path.
The gate answers before the media does
$ curl -sI https://api.wave.online/v1/transcribe HTTP/2 402content-type: application/jsonwww-authenticate: Payment …
402 Payment Required. The price, the asset, and the settlement network ride in the www-authenticate header. Pay it, retry, and the same path returns the work. Read the OpenAPI document
| Field | Observed |
|---|---|
| Status | 402Payment Required |
| content-type | application/json |
| www-authenticate | Payment … |
| Surface | api.wave.online/v1/transcribe |
| Document | Read the OpenAPI document |
Solved once, for every transport
The engine itself handles timing, integrity, sync, reliability, and metering. Add a protocol: NDI, SRT, Dante, ST 2110, MoQ, and it inherits everything already solved. No rebuilding the hard parts per format.
8 the hard parts2 live · 3 building · 3 planned
| Name | Status | What it solves |
|---|---|---|
| 01WAVE Clock | Live | One media clock, PTP (IEEE 1588 / SMPTE 2059-2) → NTP → monotonic, carries 100 ns media time plus UTC wallclock, so every stream shares one timebase. |
| 02Adapter + metering | Live | One uniform duplex adapter interface (open · send · recv · meter · close) and one wave.usage meter measure and bill every transport the same way. Real SRT, RIST, AES67/RTP, and OMT adapters ship on it today. |
| 03Integrity | Building | Each unit carries a sequence number, media-time, and a content fingerprint, so a receiver can verify it got exactly what was sent. ("We get what we send.") |
| 04A/V sync | Building | Audio and video lock to the same media time across every adapter: no drift between what you hear and what you see. |
| 05Reliability | Building | The engine supervises discovery, runs watchdogs, and reconnects on a circuit breaker, so a flaky link recovers instead of failing. |
| 06Control plane | Planned | AMWA NMOS (IS-04/05/07/08) registration, connection, and control for broadcast interop. |
| 07File & record | Planned | MXF, MP4/MKV, and BWF capture/playout alongside the live path. |
| 08Cloud fabric | Planned | EBU MXL flow nodes, the same engine, federated across the network. |
Open core
The engine core is Apache-2.0 and dependency-free C++17, an open foundation anyone can build on. Commercial adapters and edge services build on top. Open where it earns trust; metered where it earns revenue.