Your own API key, your own AI bill
Most editors that ship AI resell it to you. You pay their margin on every call, at their rate limits, under their data terms with the provider.
The BYOK plan removes that layer. You bring your own API key. The editor calls your provider account directly. Same features. Your invoice.
Where the keys go
Open License Key, then Manage API Keys.
Five providers are supported today:
- OpenAI — writing and images
- Anthropic — writing
- Gemini — writing and images
- Groq — fast inference
- AssemblyAI — speech to text, not writing
Paste a key into any row. Add one or add all five. The model picker in the editor then shows whatever you have connected.
What it looks like in use
The video runs one prompt: an article on Christmas and winter, 500 words, with images added where they fit.
The editor writes the article. It generates the images. A progress indicator shows how far along the image generation is, so you are not staring at a blank box wondering if it hung.
Then the images land in place alongside the text.
The preview matters more than it sounds
There is a preview window on the result.
What you see there is what renders on your site. Same structure, same spacing, same image placement. Not an approximation to be tidied up afterwards.
That is a property of the editor, not the AI. The content is stored as structure, so what the model produced and what your template renders are the same object.
Why teams want their own API key
Three reasons come up.
Cost. You already have a provider contract. Paying a second margin on the same tokens is hard to justify.
Limits. Your rate limits are yours. You are not sharing a pool with every other customer on the platform.
Terms. Your data agreement with the provider is the one that applies. For some teams that is a procurement requirement, not a preference.
Swapping models
A key is a switch.
Prefer Claude for long-form and GPT for images? Add both and pick per prompt. A new model ships and you want to try it? Change the key, not your code.
You are not locked to whichever provider the editor happens to have a contract with this quarter.
What you need
- An Eddyter account on the BYOK plan
- At least one provider API key
- Two minutes
bash
1
npm install eddyter
Add your keys on the license key page. Setup for the editor itself is covered in the docs.
A note on AssemblyAI
It sits in the same list but does a different job.
That key powers speech to text — dictating instead of typing. It will not write an article for you and it will not generate an image.
Worth knowing before you wonder why it is not in the writing model picker.
Common questions
Do I need keys for all five? No. One is enough.
Which one should I start with? Whichever you already pay for.
Are my keys visible to anyone? They are stored against your license key and masked in the interface.
Can I switch later? Yes. Replace the key.
Is BYOK on every plan? No, it is its own plan. See pricing.