yt-clipping-agent is a completely free YouTube clipping agent. It takes YouTube content — a video or a channel — as input and produces clips from that content, at no cost, with no paid tier, no paid requirement, and no paid option anywhere in the product. It is usable both through a first-party web interface and through an API, so that programmatic integrators can drive clipping without touching the UI.
The product intent is deliberately narrow and honest: a precision utility that turns YouTube sources into usable clips, driven either by a person working in the interface or by a system calling the API. The audience is two kinds of technical-leaning users — solo clip creators who want usable clips from YouTube content without paying, and API integrators who want to trigger clipping programmatically at no cost. The design register is competence and momentum: a sharp, no-nonsense machine that never asks for a credit card.
yt-clipping-agent is delivered as a first-party web application with an application-owned identity layer and a first-party API surface. The current delivery includes:
Actors are the Clip Creator (supplies a YouTube video or channel and the clipping goal, runs the agent, reviews resulting clips) and the API Integrator (connects the agent to its API, supplies required API credentials or keys, triggers clipping programmatically). YouTube is an external content provider, not a persona; the clipping pipeline itself is system work.
Narrow exclusions: there is no paid tier, no paid requirement, no paid option, no pricing table, no upgrade prompt, and no paid-tier visual language. Nothing in the product may require payment to use clipping, to use the API, or to retain clipping inputs, generated clips, or API configuration.
Delivery is first-party web plus first-party API. The web application owns the anonymous entry, the enrollment and verification boundary, and all authenticated working surfaces. The API is owned by the application and is reachable by an authenticated integrator who holds credentials or keys issued through the application.
Access ownership is as follows. The Landing, Sign Up, and Login surfaces are anonymously reachable — a visitor can read the entry surface and can establish or verify identity without already being signed in. Sources, Generate, Clips, and API require a verified identity, because each of them reads or writes durable person-specific state: saved sources, generated clips, and API configuration. A protected surface never owns the interaction that establishes access to itself; enrollment and verification live on their own anonymously reachable surfaces.
The API Integrator's credentials or keys are supplied before programmatic triggering, and are issued and managed inside the authenticated API surface. Programmatic clipping calls are authenticated with those credentials.
Current versus future: everything described in this document is current. No future-horizon capabilities are accepted, and none are specified here. YouTube content retrieval is external provider work; the application does not own YouTube's content, playback, or terms.
Not applicable. No reference directive in this project declares a content_source, so no source content inventory is produced.
FR-1 — Free YouTube clipping agent (explicit). As a Clip Creator, I should be able to use a YouTube clipping agent that is completely free, so that I can obtain clips from YouTube content without paying.
FR-2 — No paid option anywhere (explicit). As a Clip Creator, I should never encounter a paid tier, a paid requirement, or a paid option, so that the "completely free" promise holds across the whole product.
FR-3 — Usable via an API (explicit). As an API Integrator, I should be able to drive the clipping agent through its API, so that I can trigger clipping programmatically at no cost.
FR-4 — Self-service enrollment before first protected use (required_inference). As a Clip Creator or API Integrator, I should be able to enroll myself before first protected use, so that my clipping inputs, generated clips, and API configuration are retained for me.
FR-5 — Returning verification before accessing saved state (required_inference). As a Clip Creator or API Integrator, I should be able to verify myself on return, so that I can continue using my saved sources, generated clips, and API configuration.
FR-6 — Supply a YouTube video or channel as the clipping source (required_inference). As a Clip Creator, I should be able to supply a YouTube video or channel as the source for clipping, so that the agent has content to work from.
FR-7 — Run clipping and see generated results (required_inference). As a Clip Creator, I should be able to run clipping for the selected YouTube content and see the generated results, so that I obtain clips from that content.
FR-8 — Review generated clips in a revisitable workspace (required_inference). As a Clip Creator, I should be able to review my generated clips in a workspace I can return to, so that I can decide whether each clip is usable.
FR-9 — Configure and use API credentials or keys (required_inference). As an API Integrator, I should be able to configure the API credentials or keys the agent requires and use them to trigger clipping, so that I can drive the agent programmatically.
Product context. The Clip Creator is a solo creator who works with YouTube content and wants usable clips out of it. They arrive at yt-clipping-agent because it is completely free — no paid tier, no credit card, no upgrade path — and because it does the clipping work rather than asking them to do it by hand. They work in the interface, not through code.
Primary goal. Obtain usable clips from YouTube content without paying for the service.
Distinct accepted responsibilities. The Clip Creator supplies a YouTube video or channel as the source for clipping; supplies the clipping goal by adjusting parameters before a run; runs the agent to produce clips; and reviews the resulting clips to decide whether they are usable. They also enroll themselves on first use and verify themselves on return so their sources and clips persist.
Relevant inputs and decisions. The YouTube video or channel reference; the clipping parameters for a run; the decision to keep, re-run, or remove a clip after reviewing it; the decision to change the source and run again.
Interactions with other accepted participants. The Clip Creator shares the identity boundary with the API Integrator — both enroll and verify through the same Sign Up and Login surfaces — but their working surfaces differ: the Clip Creator works on Sources, Generate, and Clips, while the API Integrator works on API. The Clip Creator does not configure API credentials as part of their clipping work. YouTube is an external content provider whose content the Clip Creator supplies by reference; it is not a participant in the product.
Observable success. Clip blocks appear on the Generate timeline with clip IDs, start timestamps, and durations; the clips are listed as aligned rows in Clips; the person can return later and find the same sources and clips waiting; and at no point is payment requested.
Product context. The API Integrator is a technical user who wants to drive the clipping agent from code rather than from the interface. They chose yt-clipping-agent because it is free and because it exposes an API — the two facts are inseparable for them: a free tool with no API would not serve them, and an API that costs money would not either.
Primary goal. Drive the agent through the API at no cost to produce clips.
Distinct accepted responsibilities. The API Integrator connects the clipping agent to its API; supplies the required API credentials or keys; triggers clipping programmatically; and reads the returned response to confirm the result. They enroll themselves on first use and verify themselves on return so their API configuration persists.
Relevant inputs and decisions. The credential or key issued through the API surface; the request body for a clipping call; the decision to rotate a key; the decision to correct and resend a rejected request.
Interactions with other accepted participants. The API Integrator shares the identity boundary with the Clip Creator but works on the API surface, where the request builder and streaming response console live. They do not supply YouTube sources through Sources or review clips in Clips as part of their programmatic workflow; the clipping they trigger is driven by their own request. YouTube is an external content provider, not a participant.
Observable success. A key is active with a live status indicator; a request is accepted; a response streams back into the console with its status; and the recurring footer stat row confirms "COST $0.00 · RATE LIMIT NONE · KEY ACTIVE".

Open API · Unlimited Clips · $0
For solo clip creatorsand API integrators
The agent reads a YouTube video or channel, captures its transcript, selects the moments worth clipping, and returns the finished clips. Every run is free — there is no paid tier and no credit card at any stage.
yt-clipping-agent turns YouTube videos and channels into clips at no cost. The agent runs the full pipeline — YouTube URL, transcript, segment, clip — whether you drive it from the interface or call it from your own code through the API. There is no paid tier, no paid requirement, and no paid option anywhere in the product.
Nothing is held back behind a payment method and no credit card is ever requested. Your sources, generated clips, and API configuration stay available for as long as you use the agent.
Every clipping capability in the interface is the same capability the API exposes. Send a YouTube video or channel reference to yt-clipping-agent and it returns transcripts, segments and finished clips — no paid tier, no credit card, no usage cap. Solo creators can drive it from the web, and integrators can call the same agent programmatically.
Read the API surface description
Open API · Unlimited Clips · $0
For solo clip creatorsand API integrators
The agent reads a YouTube video or channel, captures its transcript, selects the moments worth clipping, and returns the finished clips. Every run is free — there is no paid tier and no credit card at any stage.
yt-clipping-agent turns YouTube videos and channels into clips at no cost. The agent runs the full pipeline — YouTube URL, transcript, segment, clip — whether you drive it from the interface or call it from your own code through the API. There is no paid tier, no paid requirement, and no paid option anywhere in the product.
Nothing is held back behind a payment method and no credit card is ever requested. Your sources, generated clips, and API configuration stay available for as long as you use the agent.
Every clipping capability in the interface is the same capability the API exposes. Send a YouTube video or channel reference to yt-clipping-agent and it returns transcripts, segments and finished clips — no paid tier, no credit card, no usage cap. Solo creators can drive it from the web, and integrators can call the same agent programmatically.
Read the API surface description
No comments yet. Be the first!