Account, billing & API
Bring your own keys (BYOK)
On the BYOK plan you connect your own provider API keys, and any job whose model runs on a provider you've connected bills 0 Framesail credits — you pay that provider directly instead. Coverage is per-job: connect only the providers you want, and anything uncovered simply runs on normal credits.
Supported providers
You can connect keys for OpenAI, Gemini, Anthropic, fal, ElevenLabs, and MiniMax. Jobs route to them by model:
- ·OpenAI — GPT models (
gpt-*), including GPT Image. - ·Gemini — Gemini text and image models.
- ·Anthropic — Claude models (
claude-*). - ·fal — all fal-hosted video models (Wan, Kling, Seedance, Hailuo, Veo).
- ·ElevenLabs — ElevenLabs TTS models.
- ·MiniMax — MiniMax speech models.
How keys are stored
- ·Encrypted at rest with AES-GCM; never returned after saving (you see a last-4 hint only) and never logged.
- ·Plaintext exists only in process memory while a covered job runs.
- ·Your keys are never used for platform-billed jobs, and platform keys are never used for your covered jobs.
Managing keys
Add, replace, or delete a key per provider at any time from the account page. An agent holding one of your fsk_ keys can also register provider keys on your behalf — useful when an agent is setting up the account end to end via MCP.
What stays included
BYOK has no monthly credit allowance — covered jobs cost 0 credits, uncovered jobs draw on credits you top up — and renders and exports stay included (export never charges credits on any plan). Full plan comparison on the plans & credits page and the BYOK page.