The same studio, from your own code.
For teams that want to start videos, read balances and fetch downloads from their own systems or an AI assistant.
- POST
/api/v1/videosMake a video: held now, charged on success, released on failure - GET
/api/v1/jobs/{id}Where a job is - POST
/api/v1/videos/{id}/publishSend to YouTube — always uploaded private - POST
/api/v1/videos/{id}/downloadsAsk for a download - GET
/api/v1/balanceThe API balance and this month’s use - POST
/api/mcpThe same, for assistants (MCP)
What it does
What it does
REST API
Channels, videos, jobs, downloads and balance under /api/v1, authorised with a bearer key.
MCP endpoint
The same keys work with assistants that speak the Model Context Protocol.
Its own balance
Videos made over the API are paid from a separate prepaid balance with monthly limits you can see. Generations use your credits, as in the Studio.
Keys you control
Create and revoke keys in the Developer console, and see usage and limits in the same place.
What it will not do
It will not open the API until you turn it on and accept the API terms.
It will not publish through a side door — videos made over the API pass the same approval gate.
It will not mix the two balances: videos are paid from the API balance, generations from your credits.
Where to start
Where to start
Read the API reference
Activate the API in the Developer console
Create a key and make your first call
Other solutions
Other solutions
- For channel operatorsRun one channel or several, and keep the last word on each.For people who run YouTube channels — often faceless ones — and want the videos made without handing over the publish button.
- For single piecesPictures, clips and voice‑overs, priced on the button.For creators and editors who need a thumbnail idea, a b-roll clip or a narration line, without starting a whole video.