A script, and an identity for the person saying it. The identity is either a description in words or a photo you supply. Everything else has a default, including the shape of the clip.

How do I get the result?

The submit call returns a run id immediately. You poll that id until the state is succeeded or failed, and a finished run carries the link to the file. Those two are the only terminal states, so there is no third case to handle.

Can I know the cost before I spend anything?

Yes. A quote endpoint returns the cost for the request you are about to make, and it is the same figure the run will use. The estimate and the charge are one number, not two that should agree.

What does a clip cost?

30 credits per second of finished video. Credits come in a pack, and the pack does not expire between campaigns.

What happens when a render fails?

You are charged only once the vendor has accepted the paid render of your clip. A failure before that point costs nothing, and so does a failure caused on our side, even when we have already paid the vendor.

How long do you keep the file?

Kept for 30 days after the run finishes, then deleted. Links expire sooner than that, so fetch the file rather than bookmarking the link.

Use case

A UGC video API you can call from anything

Send a script and a person, poll a run id, get a vertical clip back. No editor, no browser, no seat to hold. Quote the cost before you spend it.

Render one clip Create an account

The whole contract, in one paragraph

You post a script and a person. You get back a run id. You poll the run id until it finishes, and a finished run hands you a vertical clip at 1080 by 1920, with no editor involved at any point.

That is the product. The rest of this page is the detail behind it.

Four ways in, one pipeline

REST, if you are writing the request yourself. A command line tool, if you want to test something before you write any code. A TypeScript SDK, if you would rather hold an object than a URL. An MCP server, if an agent is the thing doing the calling.

None of these is a tier above another, and none of them is behind a sales conversation. They are four doors into the same render.

Two states, and why that matters

A run ends succeeded or failed. There is no third terminal state, which means your polling loop has one branch and not a family of them.

Failure carries a reason, and the reason decides the money. Billing starts when the vendor accepts the paid render of your clip. A run that breaks earlier costs nothing. A run that breaks because of us costs nothing either, even when we have already paid the vendor, because we do not charge for work we stopped, lost, or rejected ourselves.

For a pipeline that retries, this is the difference between a safe retry and an expensive one.

Costing a job before you run it

Ask the quote endpoint what a request will cost, and it answers with the number the run itself will use. That lets a scheduler decide whether to proceed, and it lets you put a real figure in front of a client before you commit to anything.

Rendering is billed at 30 credits per second of finished video. Credits live in a pack. A quiet fortnight costs nothing, because nothing is expiring while you are not rendering.

What this API does not do

It does not post your clip anywhere. It renders the file and returns it, and any publishing is yours to arrange.

It does not edit. There is no timeline, no browser editor, no drag and drop.

If either of those is what you came for, this is the wrong tool and you should know that on the first page rather than the fourth.

Start

The part that decides whether this fits your system is not the submit call, it is what your code does with a failure. Read the quickstart, make one call, and let one run fail on purpose.

Checked on 2026-09-15.

Questions

What do I send?: A script, and an identity for the person saying it. The identity is either a description in words or a photo you supply. Everything else has a default, including the shape of the clip.
How do I get the result?: The submit call returns a run id immediately. You poll that id until the state is succeeded or failed, and a finished run carries the link to the file. Those two are the only terminal states, so there is no third case to handle.
Can I know the cost before I spend anything?: Yes. A quote endpoint returns the cost for the request you are about to make, and it is the same figure the run will use. The estimate and the charge are one number, not two that should agree.
What does a clip cost?: 30 credits per second of finished video. Credits come in a pack, and the pack does not expire between campaigns.
What happens when a render fails?: You are charged only once the vendor has accepted the paid render of your clip. A failure before that point costs nothing, and so does a failure caused on our side, even when we have already paid the vendor.
How long do you keep the file?: Kept for 30 days after the run finishes, then deleted. Links expire sooner than that, so fetch the file rather than bookmarking the link.

Render a clip and compare the files yourself.