API · CLI · MCP

Same clipping. No dashboard required.

Every Katto job runs in our cloud — download, transcript, moment scoring, cut, captions, reframe, publish. The dashboard is one way to start a job. The API, the CLI and the MCP server are three more. One quota covers all four: on Creator, 25 source videos a month, up to 90 minutes each, whichever door you come through.

One request

“Take this 90-minute stream VOD, keep the 6 strongest moments, caption them in English and Spanish, and queue them for TikTok and Shorts.”

Katto downloads the VOD, scores the transcript, cuts the clips, burns word-level captions, reframes to 9:16 and schedules the posts. Your machine does nothing but send the request.

Measured worker runtime on one 20-minute video: 8 finished clips in 295 seconds (4.9 minutes). Queue and download time vary; this is not an end-to-end guarantee.

Three ways in, one agent

In your assistant
MCP

Sign in once from Claude, Cursor, ChatGPT, VS Code or Windsurf. Hosted server, OAuth 2.1 with dynamic client registration — no API key on your disk, nothing to install. 29 tools, each annotated: read-only tools are marked read-only; the one tool that spends quota says so. Prefer running it locally? npx katto-mcp with a sk_live_ key.

{ "mcpServers": { "katto": { "url": "https://mcp.katto.tech/mcp" } } }
MCP server →
In your terminal
CLI

Run the whole pipeline from your shell or a cron. --json on every command, an Idempotency-Key on every job, webhooks with --webhook. Built for cron jobs and CI, not for demos.

npm i -g katto-cli
katto login
katto clip https://youtube.com/watch?v=… --clips 6 --wait
Read the docs →
In your product
REST API

POST /v1/jobs with a scoped key (read or write), an idempotency key you choose, and an optional webhook_url. Job completion arrives as an HMAC-SHA256-signed webhook ({timestamp}.{body}, replay window 5 min). Poll with GET /v1/jobs?cursor= if you'd rather.

POST /v1/jobs  { "url": "https://youtube.com/watch?v=…" }
API reference →

One account, one quota, one job model. Re-renders and dubs never count against it.

What actually runs

  1. 1Fetch — YouTube, Twitch, Vimeo, Rumble, Zoom, Dailymotion links (or an upload).
  2. 2Transcript — WhisperX, word-level.
  3. 3Moment scoring — Miru rates every candidate on Hook, Flow, Value and Trend; you see the scores, not a black-box “virality” number.
  4. 4Cut, caption, reframe — 9:16 with active-speaker tracking; captions in 99 languages, with precise word timing in 41.
  5. 5Dub (optional) — 19 languages today: English, Spanish, French, Italian, Portuguese, Hindi, Japanese, Chinese, German, Korean, Dutch, Polish, Russian, Turkish, Indonesian, Vietnamese, Thai, Ukrainian, Arabic.
  6. 6Publish or schedule — 7 platforms, from the same job.

Nothing here runs on your machine. That's the point: an agent, a cron job or a backend can trigger a full pipeline from a single request.

What you get that you’d otherwise have to build

Hosted OAuth 2.1 + DCR
For MCP clients; keys never appear in a browser URL.
Dual auth
On the same endpoint: an OAuth grant, or an Authorization: Bearer sk_live_… header from a script.
Scoped keys
Read-only keys for dashboards and monitors, write keys for pipelines.
Idempotency keys
On job creation — retry safely, never double-spend a video.
Signed webhooks
HMAC-SHA256 with timestamp, SSRF-guarded on our side.
Annotated tools
MCP clients can tell at a glance which of the 29 tools read, which spend quota, and which ones cancel work or post publicly.
Per-video pricing
No per-minute meter, no credits, no separate agent quota.

Who uses it this way

A weekly podcast, on a cron.
katto clip $EPISODE_URL --wait --json | jq '.clips[].url' every Monday. The host never opens a dashboard.
An agency with a pipeline.
Their backend posts jobs with client-specific idempotency keys and consumes the webhook; clips land in the client's review folder.
A creator in Claude.
“Clip the best moments from this episode and reframe them for TikTok” — then “dub clip 2 in Spanish” — without leaving the conversation.

Start free

2 videos a month, no card. The API, CLI and MCP server are included on every plan, free tier too.