Model access and invocation strategy
Settings should minimize ambiguity. The page needs to show what is configured, what each plan means, and what remains blocked in the runtime.
Stored configuration
- Providers
- 0
- Enabled providers
- 0
- Models
- 0
- Execution readiness
- Blocked
Current facts only: provider and model records below come from real persistence, and the forms on this page write directly to the database.
Model Providers
Not configured
No enabled provider exists for model execution.
Models
Empty
No model definitions have been stored yet.
Plan guide
- `managed` is the future platform-hosted path and the clearest default for members.
- `user_key` is for bring-your-own-key plans and remains honestly unimplemented.
- `hybrid` should only be selected when both paths are intended later.
- `member` access should be reserved for gated plans that require login.
Provider Config
Add provider
This writes a real provider record to the database. Connection testing and encrypted secret storage are not implemented yet, so do not treat this as production-grade secret management.
Model Config
Add model
Models are stored against a real provider record. If you mark one as default, previous defaults for that provider are unset automatically.
Invocation legend
managed
Intended for platform-managed execution once the adapter exists.
user_key
Bring-your-own-key plan. Not wired yet, so the UI should never pretend otherwise.
hybrid
Reserved for mixed platform and BYOK strategies when both paths exist.
Providers
Stored providers
No providers are configured yet.
Models
Stored models
No models are configured yet.