Providers
Provider auth, filtering, and model override contracts.
Providers are model backends AlphaBase can route through. Provider metadata is sourced from Models.dev and then merged with your connected credentials and local overrides.
Runtime Provider APIs
Useful server routes:
GET /providerGET /provider/authGET /provider/capability-indexPOST /provider/:providerID/oauth/authorizePOST /provider/:providerID/oauth/callbackGET /provider/model-search?q=<query>
Connect A Provider
Typical flow:
- open provider UI or
/connectflow - authenticate via OAuth or API key
- confirm provider appears in connected list
- choose a model
Filter Provider Inventory
Use config-level filters:
{ "enabled_providers": ["openai", "anthropic", "ollama"], "disabled_providers": ["openrouter"]}enabled_providers is an allowlist. If present, all non-listed providers are hidden.
Provider Override Schema
Each provider.<id> can override provider or model behavior.
{ "provider": { "openai": { "options": { "apiKey": "{env:OPENAI_API_KEY}", "timeout": 300000, "setCacheKey": true }, "models": { "gpt-5": { "options": { "reasoningEffort": "high" }, "variants": { "fast": { "disabled": true } } } } } }}Supported common option fields:
apiKeybaseURLenterpriseUrl(notably for GitHub Enterprise Copilot auth)setCacheKeytimeout(numberorfalse)
Custom Provider Pattern
You can define non-default providers via provider records (for example OpenAI-compatible gateways), then route models through them.
Model Search (Model-First Onboarding)
/provider/model-search groups matching models by canonical family and ranks provider options by first-party/bundled/connected status. This powers “add model first, then choose provider” workflows.
Troubleshooting
If provider is configured but unusable:
- check
runtime/capabilities - verify env key scope and endpoint URL
- verify provider is not excluded by
enabled_providers/disabled_providers - confirm timeout/baseURL overrides are valid
See Troubleshooting.