Your video editor is now an API call.
Describe a cut, POST it, get a finished file back as a URL. No NLE, no seat, no render farm, no one in the chair.
POST /v1/editor/projects/proj_8f21/export
{
"format": "mp4",
"resolution": "1920x1080",
"quality": "high"
}
202 Accepted
{
"id": "exp_2c7d",
"status": "queued",
"progress": 0,
"outputUrl": null
}
Poll the export id, or subscribe to /v1/render/{id}/events; outputUrl is the finished cut.
- create
- POST /v1/editor/projects
- export
- POST /v1/editor/projects/{id}/export
- auth
- Authorization: Bearer <key> — or pay per call over x402
Send JSON. Get a URL back.
Create a project, post an export, read outputUrl. Auth, scopes, and metering federate through api.wave.online, so it is one WAVE key and pay-per-render over 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 in alpha, documented in the published OpenAPI document and callable now.
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 — 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.