AI clipping API: automate shorts with one request in, one webhook back
Clipping AI has an AI clipping API: one POST with a video URL returns 3 to 15 vertical clips with captions, and a webhook tells you when they are ready. It draws the same minutes as the dashboard ($12/month for 100 minutes, no per-call fee).
The whole automation loop is two HTTP messages. You POST a video URL with an API key and a webhook address; when processing ends, Clipping AI sends exactly one signed webhook carrying clip titles and durable download links. No polling, no timeout guessing.
API calls draw from the same minute balance as the dashboard, with no separate meter and no per-call pricing, which is what keeps an always-on pipeline affordable.
For agent-driven automation (Claude, ChatGPT, custom agents) the same account also exposes an MCP server; documented on its own page.
What the clipping API costs per source minute
| Plan | Price | Source minutes monthly | Per source minute |
|---|---|---|---|
| Starter | $12/month | 100 | $0.120 ($0.100 billed yearly) |
| Creator | $29/month | 300 | $0.097 ($0.081 billed yearly) |
| Pro | $59/month | 750 | $0.079 ($0.066 billed yearly) |
API calls, dashboard jobs and MCP tool calls all draw from the same balance; there is no separate API plan and no per-request fee. Trims, hook edits and re-renders burn no minutes.
Your first video is free up to 60 minutes, then you get 20 free minutes a month, with no card requested.
The loop, end to end
Start a job with one request:
curl -X POST https://clip.zes.codes/api/process \
-H "Authorization: Bearer osk_..." -H "Content-Type: application/json" \
-d '{"url": "https://youtube.com/watch?v=...", "acknowledged": true,
"webhook_url": "https://your-server.com/hooks/clippingai",
"webhook_secret": "your-shared-secret"}'
The response returns a job id immediately. Minutes later, once the clips are cut, subtitled and archived, Clipping AI POSTs once to your webhook URL with the job outcome, clip titles and download links durable enough to fetch later. A failed job fires the webhook too, so your pipeline never hangs on silence.
Verifying the webhook
If you passed a webhook_secret, the request carries an
X-Clipping AI-Signature header of the form
sha256=<hex>: the HMAC-SHA256 of the raw request body under
your secret. Recompute it and compare in constant time:
expected = "sha256=" + hmac.new(secret, raw_body, hashlib.sha256).hexdigest()
hmac.compare_digest(expected, request.headers["X-Clipping AI-Signature"])
Reject anything that does not match and you have shut the door on forged deliveries.
Using it from n8n, Zapier or Make
No dedicated node is needed: the flow is a generic HTTP Request step POSTing to /api/process, then a Webhook trigger that receives the completion payload and fans out to whatever comes next — posting to socials, dropping links in Slack, logging to a sheet. That two-step shape is the whole integration, which is why generic nodes cover it. There is also an importable n8n workflow that wires the whole
loop, including channel watching, Telegram approval and scheduled publishing.
A weekly pipeline in one cron line
Because the API is one POST, scheduling is whatever scheduler you already use. A cron job submitting the latest episode URL every Monday, or an agent watching a feed. The webhook does the second half, so nothing stays running in between. The whole loop is a single curl:
curl -X POST https://clip.zes.codes/api/process \
-H "Authorization: Bearer $CLIPPINGAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "'$EPISODE_URL'", "webhook_url": "https://your-server.com/hooks/clippingai", "webhook_secret": "'$SECRET'"}'
What automation costs
API and MCP calls draw from the same minute balance as the dashboard. No per-call price, no separate API tier and no automation surcharge. As of August 2026 that is not the market default: the mainstream tools meter their APIs per source minute or per operation, on top of subscription tiers, so an always-on pipeline runs with a taxi meter ticking. the hosted plans are flat-rate:
On Clipping AI Cloud: the first video clipped whole up to 60 minutes, then 20 minutes a month with a watermark and no card, then flat plans starting at $12/month (100 minutes) to $59/month (750 minutes), or $49.17/month on yearly billing.
Agents instead of scripts
If an AI agent rather than a script drives the pipeline, the same account exposes a native MCP server with six tools covering process, status, clips, quota, subtitles and publishing. The endpoint, tool table and client setup live on the MCP server and API page.
Questions people ask
- Is there an n8n integration for Clipping AI?
- Yes: an importable workflow at /n8n-youtube-shorts-automation watches a YouTube channel, clips each video, sends the clips to Telegram for approval and schedules the approved ones to your socials. Nothing forces you to use it, though: the integration is just an HTTP Request node posting to /api/process plus a Webhook trigger.
- Do automated API calls cost more than using the dashboard?
- No. API and MCP usage draws from the same minute balance as the dashboard with no per-call pricing: 20 free minutes a month on the free tier and flat paid plans from $12/month.
Where these numbers come from
- Competitor API metering checked 2026-08-04 on public pricing and developer documentation.