Media

Money

Dispatch

Company

WAVE · Encode

Every codec, encoded to spec.

Media infrastructure for the agentic internet. One POST /v1/encode reaches the whole codec plane, hardware and software: H.264, HEVC and AV1, metered to the minute, settled per call on the WAVE rail.

Encode matrix60 frames · 640×360 · 30 fps · 2 Mbps · one call each
codec · encoderpath032,730 Boutputthroughput
H.264 · libx264software32,730 B1,818 fps
H.264 · h264_videotoolboxhardware19,974 B448 fps
HEVC · hevc_videotoolboxhardware16,733 B480 fps
AV1 · libsvtav1software16,659 B625 fps

Same 60 frames, half the bytes. libsvtav1 returns 16,659 B where libx264 returns 32,730 B, and the call that asks for either one is the same four lines.

Also on the plane: libx265 for HEVC in software, h264_nvenc and hevc_nvenc on discrete hardware at 12.9× realtime. QuickSync and AMF are not in this plane, so they are not on this page.

the call
POST /v1/encode
host: api.wave.online
authorization: Bearer <key>
content-type: application/json

{"codec": "libx264"}
what came back
200 OK
x-wave-meter: wave_encode_minutes

{"codec":"libx264",
 "frames":60,
 "bytes":33950,
 "fps":331.5}
$0.02 USDC per callsettled on Base, no accountquoted by the route itself: 402 → maxAmountRequired 20000

One call, every codec

One call returns the encoded bytes, the frame count, and the throughput. Every number above came off a real 60-frame encode, not a vendor slide.

There is no account and no subscription in the way. The route quotes its own price, you pay per call in USDC on Base, and the same bearer key and meter run every other WAVE service.

Four encoders are measured here and two hardware families are not. QuickSync and AMF have no measurement in this plane, so they get no claim on this page. What the plane cannot do is printed next to what it can.

endpointPOST /v1/encode {"codec"} → {frames, bytes, fps}
decodePOST /v1/decode {"codec"} → round-trip
authAuthorization: Bearer <key> (via gateway)
healthGET /health → {"ok":true,"service":"wave-encoder"}

A codec a machine can buy

Encoding on the WAVE plane is not a one-off job. It is a typed result your agents can pay for and pipe straight into the next WAVE service, under one key and one meter. Video and audio go in, encoded bytes come out, and the meter reads the same whether a person or an agent made the call.

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