Skip to main content
Creatorline runs AI creators: a persona with a consistent face, voice and audience, posting on a schedule. The API gives you every piece of that pipeline except the human judgement — generate media as a specific creator, then publish it to their connected accounts. Three surfaces, one implementation. They share the same key, the same validation, and the same credit accounting.

REST

Your backend, your scripts, anything that speaks HTTP.

CLI

crl — terminals, CI, and coding agents.

MCP

Claude Code, Cursor, any MCP client.

Quickstart

1

Create a key

In the studio, go to Settings → API and create a key with the write scope. The key is shown once — copy it now.
2

Check it works

3

Generate something

Returns immediately with a job handle and the credits it charged:
4

Poll until it's done

queuedprocessingsucceeded, then output[0].url is your image.
Result URLs are time-limited. Download the bytes rather than storing the link.

The shape of the thing

A photo takes ~30 seconds and a video several minutes, so no endpoint blocks on a run. You get a job handle and poll it. The run is durable: it survives your process dying, and you can rejoin it by id at any time.
Do not hardcode model ids or parameter names. GET /v1/models returns every tool, every model, and the exact inputs and parameters each accepts — so a model added to the platform is usable from your code with no change on your side.
POST /v1/generations/cost prices a run without starting it, using the same function the debit uses. A failed or moderation-blocked run is refunded automatically.
A post is created at pending_review and publishing is a separate, explicit call. If you want a human to approve, simply never call publish — the post waits in the studio’s review queue. See Publishing.

What you can do