Settings · 7 minutes
Add, validate, use, and remove a personal provider key
Use your own OpenAI, Anthropic, Google, or Moonshot/Kimi key without exposing it in the desktop UI.
Use this guide with Avori
Open Avori, then keep this guide beside it while you follow the steps. Avori does not receive the page text, your account, your project, or anything you typed.
If nothing opens, start Avori normally. The written steps still work.
Before you start
- Avori Pro is active, or you have an eligible Studio seat.
- An active provider account and personal provider key.
- You understand that the provider bills usage directly.
Plan and model funding
Using your own AI provider key is available with Pro or an eligible Studio seat. Your provider bills usage of your own key directly under its own prices and limits. It does not use trial credits or Avori Balance.
Say this in ordinary language
After choosing a personal-key model: Explain this project in three short points. Do not change anything.
Steps
-
1
Open Settings, then Keys.
What you should see: OpenAI, Anthropic, Google, and Moonshot/Kimi key controls appear.
-
2
Paste one provider key and save it.
What you should see: Avori validates the key and later shows only configured status, never the raw value.
-
3
Open the model picker, choose Keys, and select a supported model.
What you should see: The active model and personal-key funding source are visible.
-
4
Send the safe prompt above.
What you should see: The answer completes without reducing Avori Balance.
-
5
Return to Settings, Keys, and remove the provider key.
What you should see: That provider returns to not configured and its key-only models become unavailable.
What Avori may change
Your encrypted personal provider key is saved in or removed from Avori's protected key storage. It is not written into the project.
How to verify it worked
Check the provider's usage dashboard for the request and confirm Avori Balance did not decrease.
Undo or recover
Remove the key in Settings and revoke it in the provider dashboard if it may have been exposed elsewhere.
Common problems
- A key can be valid but lack model permission or provider balance.
- Never paste a provider key into chat, a project file, or a support report.