Available on Pro & BYOK
Drive the whole pipeline
from your agent.
Framesail's REST API and MCP server let Claude Code, Claude Desktop, and any agent produce finished long-form video — script to MP4 — programmatically.
claude mcp add --transport http framesail \
https://api.framesail.com/mcp \
--header "Authorization: Bearer fsk_..."Two surfaces, one auth
REST or MCP — same pipeline.
Both surfaces use the same fsk_ key and run the exact same generation, ownership, billing, and rate-limit code paths. Pick whichever fits your client.
REST API
Plain HTTPS against api.framesail.com, with a machine-readable OpenAPI spec at /openapi.json. Best for scripts, SDKs, and custom backends.
MCP server
A streamable-HTTP MCP endpoint at /mcp. Connect Claude Code, Claude Desktop, claude.ai, Cursor, or any MCP client and get 65 tools that wrap the same pipeline.
One brief in, a finished video out.
Your agent calls the steps in order; Framesail guarantees that minute 7 of the video is consistent with minute 1. State lives server-side, so a run can stop for hours and resume in a fresh session.
- 01Create a project from a video concept
- 02Generate or upload a script, then scan it into characters, environments & voice blocks
- 03Bind voices and render word-timed voiceover
- 04Plan the storyboard against your channel's art, narrative & director styles
- 05Render every segment's images and video
- 06Build the timeline and export a finished MP4
Bring your own keys. Pay zero credits.
On the BYOK plan, register your own OpenAI, Gemini, Anthropic, fal, ElevenLabs, or MiniMax keys — or send them per-request — and any job on those providers runs on your key for zero Framesail credits. Coverage is per-job, so a mixed pipeline only bills for what you don't cover.
openai · gemini · anthropic
fal · elevenlabs · minimax
Get set up
Connect in three steps.
Subscribe to Pro or BYOK
API & MCP access is included on the Pro and BYOK plans. Creator is web-app only.
Create an API key
On your account page, generate an fsk_ key. It's shown once — copy it somewhere safe.
Connect your agent
Point your MCP client or HTTP client at Framesail with the key as a Bearer token. That's it.
Developer questions
API & MCP, answered straight.
Who is the API & MCP for?
Anyone who wants to drive Framesail from outside the web app — running a faceless channel at scale, wiring video generation into your own product, or letting an agent like Claude produce videos end to end. Framesail owns the project database, asset continuity, voiceover timing, and the render pipeline; your agent owns the workflow.
Which plans include it?
Pro and BYOK. Pro runs jobs on platform credits; BYOK lets you bring your own provider API keys so covered jobs bill zero credits. Creator is web-app only by design. See the pricing page for current rates.
What's the difference between the REST API and the MCP server?
They're two surfaces over the exact same pipeline and the same authentication. REST is best for scripts and SDKs; MCP is best for agent clients like Claude Code, Claude Desktop, and Cursor. The MCP tools are thin wrappers over the REST endpoints — pick one surface per run.
How does authentication work?
You create a long-lived fsk_ API key in the web app and send it as an Authorization: Bearer token. The same key works for both REST and MCP. For security, agents can't mint or revoke keys — only a signed-in browser session can.
What is BYOK?
Bring Your Own Keys. Register your own OpenAI, Gemini, Anthropic, fal, ElevenLabs, or MiniMax keys and any job on those providers runs on your key and bills zero Framesail credits. Coverage is per-job, so a mixed pipeline only bills for the jobs you don't cover.