Use case

A catalogue that fills itself.

Render clips for your feed or catalogue from typed jobs: the four picks, the length and the shape as fields. The same engine as the studio.

Read the docs Get a key
POST /v1/videos
curl https://api.corny.studio/v1/videos \
  -H "Authorization: Bearer $CORNY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "describe": "she laughs on a beach at golden hour",
    "seconds": 8,
    "aspect": "portrait"
  }'

# { "id": "job_…", "status": "queued" }

  • Typed, not tuned

    Picks are fields. No prompt to maintain.

  • Predictable cost

    Each length has one price in credits.

  • What you test ships

    The API renders exactly what the studio does.

Generating adult content at catalogue scale

A catalogue or a feed needs volume, variety and a cost you can plan. Running your own generation stack means choosing models, tuning prompts that drift with every model update and paying for GPUs whether they are busy or not. Corny turns that into typed jobs: the picks, the length and the shape are fields, and each combination has one price.

Because the picks are fields and not a prompt, the same job gives the same kind of scene every time. You can build a catalogue the way a database is built, from rows of picks, and change one field to make the next variant. The same rows can be rendered again later, in a new shape or at a new length, without rewriting anything.

Render clips from typed jobs with the Corny API

Send POST /v1/videos with catalogue picks: the character, what she wears, how she is posed and where, plus the length and the shape. When a row needs something the catalogue does not hold, send a describe sentence instead. Every job returns an id at once. Poll GET /v1/jobs/:id until the clip is ready and fetch it from a signed link.

Characters built in the studio keep their accepted face in every job, so a recurring performer on your platform looks the same across hundreds of clips. Clips run up to ten seconds with the sound of the scene, in portrait for mobile feeds or wide for a desktop catalogue. You choose both per job, so one character can fill a vertical feed and a wide catalogue page from the same recipes.

Test a recipe by hand in the studio first. The API renders exactly what the studio does, so what you approve there is what ships. Every character is a fictional adult made with AI, and every job has to follow our content policy alongside your own platform rules. Keeping your approved recipes as data on your side makes that review a one time step per recipe.

Predictable cost per clip in credits

Each length, size and quality has one price. A longer, bigger or sharper take costs more. So you can price a catalogue before you render a single job.

The API is open to every account, and plans add credits every month, cheaper each on a bigger plan: Developer is $99.90 for 6,000. New accounts start with 50 credits to test recipes in the studio first. For larger volumes, Enterprise is an invitation to talk about what you have in mind.

Questions people ask

Can I generate adult clips through an API?

Yes. POST /v1/videos takes catalogue picks or a describe sentence, and the finished clip arrives on a signed link. Every clip follows our content policy.

How is the API priced?

In credits, by length, size and quality: from 14 for a small five second clip to 114 for a large ten second one at high quality.

Does the API render the same quality as the studio?

Yes. It is the same engine, so a recipe you test in the studio renders the same way through the API.

The features behind it

Render her from your code.

Make a key in the studio and send your first job in minutes.

Read the docs Get a key