WAVE · Editor

Your video editor is now an API call.

Describe a timeline in JSON, POST it, get a finished cut back as a URL. Cut, splice, and render video from your code — no NLE, no seat, no render farm, no one in the chair.

endpointPOST /editor/render {"timeline"} → {url}
authAuthorization: Bearer <key> (via gateway)
healthGET /health

Send JSON. Get a URL back.

Send a timeline as JSON to /editor/render; a URL comes back — the finished cut. Auth, scopes, and metering federate through api.wave.online, so it's one WAVE key and pay-per-render via x402 — no editor license, nothing to install, no seat to expense. The edge front-door is live today; the render contract runs on the WAVE gateway (alpha), documented and callable, not a benchmark.

Video becomes a stage in a pipeline.

One WAVE key, and Editor composes with the rest of the plane: pull source over WAVE transports, cut and render here, hand the URL straight to the next spoke. Video stops being a person's task and becomes a stage in a pipeline — cut, splice, and render as programmable as any other call on the WAVE plane.

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