Direct-billing image workflow
Run selected image steps on your own provider account.
- 1Add your provider key
- 2Generate prompts with AI-FLOW
- 3Run image nodes with your key
- 4Export generated assets
AI-Flow
BYOK AI Workflow Builder
Build workflows with your own AI provider keys when you want cost control, direct billing, and flexible model access.
Nano Banana 2
Google
GPT Image 2
OpenAI
Claude Sonnet 4.6
Anthropic
“Subtle fashion film. Woman wearing tortoiseshell sunglasses, slight confident head turn, warm studio light gliding across the lenses. Hair moves gently. Slow motion, luxury campaign feel. No background change, keep studio setting.”
Seedance 2
ByteDance
Flux 2 Max
Replicate
Nano Banana 2Google
GPT Image 2OpenAI
Claude Sonnet 4.6Anthropic
“Subtle fashion film. Woman wearing tortoiseshell sunglasses, slight confident head turn, warm studio light gliding across the lenses. Hair moves gently. Slow motion, luxury campaign feel. No background change, keep studio setting.”
Seedance 2ByteDance
Flux 2 MaxReplicate
Control AI costs with your own keys
Use your own keys when you want direct provider billing, and use AI-FLOW credits when you want to try a model without setup.Bring your own API keys
Connect provider keys for OpenAI, Anthropic, Replicate, Google, and more so matching nodes can run on your own provider accounts.
Bring your keys
- OpenAI
- Anthropic
- Replicate
- xAI
Pay providers directly at their rates
or
Use platform credits
- No setup required
- No keys needed
Start immediately, no configuration
Use keys or credits depending on the model
Use your own keys when you want direct provider billing. Use AI-FLOW credits when you want to try a model without setup.
10 models available
- GPT
- Claude
- Gemini
- GPT
- Claude
- Gemini
BYOK workflow examples
Practical workflows with clear inputs, model steps, and final outputs.
Mixed provider workflow
Use your keys for some nodes and credits for others.
- 1Use your OpenAI key for text
- 2Use AI-FLOW credits for a model you are testing
- 3Combine both outputs
- 4Keep the workflow reusable
Cost control workflow
Choose which steps should use your provider billing.
- 1Identify expensive generation steps
- 2Assign those nodes to your own keys
- 3Run smaller steps with credits
- 4Review final outputs
Team experimentation workflow
Keep setup flexible while trying new models.
- 1Start with platform credits
- 2Add keys for models you use often
- 3Reuse the same workflow
- 4Control provider usage over time
Related workflow pages
Frequently Asked Questions
Do my API keys stay private?
AI-FLOW is designed so your provider keys can be stored and used for matching nodes without exposing them in workflow outputs or public pages.
Can I choose which nodes use my own keys?
Yes. BYOK is useful when you want specific provider nodes to run on your own account while keeping other parts of the workflow flexible.
Do I still need AI-FLOW credits if I bring my own keys?
You can use your own keys for supported provider nodes and use AI-FLOW credits when you want to try models without setting up a provider key.
Why bring my own API keys?
Bringing your own keys can help you manage provider billing directly, use existing accounts, and control which AI services your workflows depend on.
Can I mix BYOK and platform credits in one workflow?
Yes. You can use your own keys for some nodes and AI-FLOW credits for others, depending on the providers and models you want to use.