DOCUMENTATION / Self-hosting
Local previewConfigure your AI provider
Add, test, replace or remove your own research key.
- Runs on
- Your local account and research worker
- Before you start
- The local quickstart and your own OpenAI API key
On this page
Open your local account
Open your running localhost installation, then create or sign in to a local account and choose Account → AI provider. This setting is on your local installation, not the hosted account. Check the hostname and port before entering a key.
You should see The local account sidebar shows AI provider and a masked OpenAI API key field.
Test and save your key
Enter your own OpenAI API key in the password field and select Test & save. The server checks authentication and required model access, then stores the key encrypted for your account. The key is never included in an MCP configuration.
You should see The provider is shown as configured. No report has been generated.
Run an approved test
Submit your own public domain in the app. This is the point where research uses your provider account. Check delivered comparisons, evidence and limitations, not only the terminal job state.
Replace or remove access
Use the same screen to replace or remove the saved key; no worker restart is needed. New and queued work uses the updated configuration. Already running work may retain the key it loaded at start. Removal here does not revoke the key at the provider.
Troubleshooting
Validation succeeds, but research fails
Validation checks authentication and model visibility. A report also needs provider billing capacity and successful inference. Inspect the report's sanitized failure state; do not keep resubmitting blindly.
The worker is not ready
Run docker compose ps from the installation folder. Web, worker and gateway should be healthy. Check the local troubleshooting guide before starting another report.