Media

Money

Dispatch

Company

WAVE · Codec

Codec benchmarking your agent can run at the edge.

Point WAVE at any video workflow and get back {status, bench} — live health and reproducible codec benchmarks across 2 endpoints. Pay by the call: no account, no subscription, no SDK to install.

240p
3.42
380 kbps
360p
3.81
720 kbps
540p
4.12
1.4 Mbps
720p
4.31
2.8 Mbps
1080p
4.47
5.2 Mbps
rate-distortion · av1 vs h.264-38% bitrate at equal MOS
380k1.4M 5.2M
statusbenchencodedecodestorepay-per-call
$ curl -s https://codec.wave.online/v1/healthz
{"ok":true,"failClosed":true,"bindings":{"codecService":true}}

Two endpoints, one runtime

One runtime exposes live health and reproducible benchmarks for the codec service. Auth, entitlement, and metering run through api.wave.online; this worker renders the front-door and forwards the billable work.

endpointGET /v1/mlvc/status → {status}
endpointPOST /v1/mlvc/bench → {bench}
authAuthorization: Bearer <key> (via gateway)
healthGET /v1/healthz

Codec intelligence a machine can act on

Because it lives on the WAVE protocol plane, a benchmark isn't a dead-end report — it's a typed result your agents can pay for and pipe straight into routing decisions, all under one key and one meter. Codec evaluation becomes something machines buy and act on autonomously, not a lab task someone has to hold.

Federated — auth, entitlement, and metering run through api.wave.online; this spoke renders the front-door and forwards the rest.