Faceless Video API: Create Videos From Code or Claude

Making one video in a dashboard is straightforward. Making thirty exposes every repetitive step: open the form, paste the next topic, choose the same settings, submit, and come back later for the file. The API exists for the point where that repetition becomes the work.

There are two ways to use it. Developers can call the REST API directly. People who prefer a conversation can connect Claude and request videos in plain language. Both use the same formats, account balance, and finished-video library as the main app.

What launched

• A REST API at /api/v1 for creating videos, checking progress, previewing credit costs, uploading assets, and managing completed work.
• An MCP connector for requesting the same work from Claude, Claude Code, Cursor, or another compatible client.
• Account sign-in for the Claude app, without copying a personal API key into the chat.
• Personal API keys for code integrations, created and revoked from Settings.

How the API works

Video creation is asynchronous. POST a topic and formatId to /api/v1/videos, and the response immediately returns a video id and the credit cost. Use that id to check progress while the video is being made. When the status becomes COMPLETED, the response includes the finished MP4 URL.

1. 1POST /api/v1/videos with { topic, formatId } -- the 202 response includes the video id and creditsCost.
2. 2GET /api/v1/videos/{id} every minute or so -- the status moves through PENDING, PROCESSING, and RENDERING.
3. 3When status is COMPLETED, videoUrl is your finished video. Download it, post it, or pass it to the next step of your workflow.

GET /api/v1/formats returns the available formats and the inputs each one accepts. That includes duration options, format-specific fields, and cast slots for character videos. You can keep the recommended model defaults or choose models for the script, voice, images, animation, and music when a workflow needs more control.

Creating videos from Claude

The MCP connector is the no-code route. Add the connector in Claude, sign in with your account, and describe the video you want. Claude can list suitable formats, preview the credit cost, create the video, check its progress, and return the finished link in the conversation.

The connector can also list voices, check your balance, remove unwanted videos, and upload character references or music. Claude Code and Cursor use a personal API key for the same tools.

Three automation recipes

1. The topic-list channel

Keep approved topic ideas in a Google Sheet or Notion database. A scheduled n8n or Zapier workflow can read the next row, create the video, wait for completion, and place the MP4 in a review folder. Keep a human approval step before publishing; automation is good at moving work, not deciding whether a video is worth posting.

2. The repurposing pipe

Some formats accept a source URL. A script can watch your own RSS feed, pass a new article URL in formatInputs, and create a draft video from it. The same pattern works for newsletters and product updates you own. Review the script before publishing, especially when the source contains quotes, dates, or figures that may need context.

3. The Claude producer

Claude is useful when the workflow still needs judgment. Plan a week of topics in one conversation, compare formats and costs, then create the videos one at a time. You can review each result before deciding whether the next topic deserves the same treatment.

Pricing and account control

API access is included in every paid plan, without a separate API subscription. Videos use the same credit pricing as the dashboard. Before creating one, call POST /api/v1/videos/preview-credits with the intended format and settings to see the exact cost.

Personal keys can be revoked from Settings, and Claude connections can be disconnected from the account that approved them. The credit ledger shows creation charges and automatic refunds for failed renders.

Get started in 5 minutes

1. 1Open Settings, go to API, and create a personal key. For Claude, use the connector flow instead.
2. 2GET /api/v1/formats to choose a format, or start with ai-images-short.
3. 3POST your first topic to /api/v1/videos and poll until COMPLETED.
4. 4Use the endpoint reference at /developers when you need optional inputs, uploads, or a copy-paste request example.