Skip to main content
This walkthrough removes the background from a clip: the lead template, and a synchronous one, so there is no polling: the run call returns the result.

Base URL

All API calls go to one host:
Every response is wrapped as { "success": true, "data": … }; errors carry { "success": false, "errorCode": … }.
1

Get a key

Create one at Workspace → Your Account → API Keys with the For skills preset, and export it:
2

Check who you are (free)

3

Upload material

Skip this step if your video is already at a public https url: a run accepts the url directly. For a local file, mint a ticket and post the file to it:
The file call needs no API key: the ticket is a one-time, single-purpose credential, safe to use in a shell.
4

Estimate (free)

Blockers are typed (INSUFFICIENT_CREDITS, IN_FLIGHT, SCOPE_DENIED, RECIPE_NOT_ALLOWED, SPEND_CAP_REACHED): branch on codes, never parse prose.
5

Run: the response is the result

The call holds open while the GPU mattes the clip (~40-90s), then:
The webm carries a true alpha channel, ready to composite. editorPath (on askeditor.com) opens the same cutout as an editable canvas: see The editable canvas. Retrying the identical call returns "cached": true and charges nothing.
Queued templates (tighten, launch-cut) run through the MCP connector and resolve via GET /v1/jobs/{id}.