◆ Docs

Drive ClipWisp headless.

Everything the studio does is callable: a REST API, the clipwisp CLI, and an MCP server your agent talks to directly. Auth is a per-user API key — create one in Settings → API keys (shown once, prefixed cw_).

◆ REST API

One key, every capability.

Send your key as a bearer token. Sources, candidate scans, renders, and packaging are all plain JSON over HTTPS with typed error codes and idempotent renders. Sources: YouTube, TikTok, X/Twitter, Instagram, Twitch & Kick VODs, Vimeo, Reddit — or direct uploads up to 2 GB.

# add a source
curl -X POST https://api.clipwisp.io/api/v1/sources \
  -H "Authorization: Bearer cw_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.youtube.com/watch?v=..."}'

# scan it for moments, then render candidate #1
POST /api/v1/creator-clips/candidates   { "sourceId": "src_..." }
POST /api/v1/creator-clips/render       { "sourceId": "src_...", "candidateId": "...", "idempotencyKey": "..." }

Every non-success response includes a stable code alongside a human-readable detail, so scripts can branch without parsing prose.

◆ CLI

URL → rendered clip in three commands.

$ clipwisp login --api-key cw_YOUR_KEY
$ clipwisp sources add "https://youtu.be/..." --wait
$ clipwisp clips find src_... --preset 30_60
$ clipwisp clips render src_... --candidate 1 --wait --out clip.mp4 --srt clip.srt

Built for scripts and agents: --json on every command prints pure API JSON to stdout, and exit codes are the contract (0 ok, 2 API error, 3 timeout, 4 unsupported input).

The CLI ships to customers on request rather than through a public registry. Everything it does is the REST API above, so nothing here is gated behind it.

◆ MCP server

Give your agent the studio.

Nine tools — add/list/get sources, find and revise moments, render, check status, fetch captions, and inspect usage — over the Model Context Protocol. The server is hosted, so an MCP client that speaks HTTP needs only a URL and your key:

Endpoint:  https://mcp.clipwisp.io/mcp
Transport: Streamable HTTP
Header:    Authorization: Bearer cw_your_key

Clients limited to stdio can run the server locally — mail support@clipwisp.io for the build. It reads the key from CLIPWISP_API_KEY in the environment your MCP client gives it, and exits at startup if that is unset. It is a thin client over the REST API above either way, so an agent that can make HTTP calls needs nothing from us to drive the whole pipeline today.

Renders accept an idempotencyKey, so agent retries reuse the original render instead of creating duplicate work.