Configure AI Provider
Bring your own key and model for OpenStar agent calls.
OpenStar keeps BYOK as a trust and cost-control strategy. It is not the core product value.
Chat requires a working provider
BYOK should not block onboarding, but Chat cannot produce real agent answers without a configured provider, model, and API key.
Provider fields
| Field | Purpose |
|---|---|
| Provider | Names the provider family or OpenAI-compatible route. |
| Model | Selects the exact model used for agent calls. |
| Base URL | Points custom or gateway providers to the right endpoint. |
| API key | Stored server-side after encryption. |
No silent fallback
If the configured provider, model, base URL, or API key fails, OpenStar should surface the failure. The app should not silently fall back to a different model or fake a repo answer.
Why BYOK exists
Control
Users choose provider, model, base URL, and key.
Cost clarity
Seed users can test the agent without hidden model resale.
Enterprise path
Teams can later map Chat to approved provider gateways.
Expected behavior
A provider failure should be visible and actionable. It should not be hidden behind a weaker model, generic response, or fake repository answer.