Platform
Provider Access
Register LLM providers, store credentials safely, control status, and run health checks.
What this menu does
Maintain the approved upstream AI services available to platform model configuration.
Where to find it
Platform Admin navigation: LLM Management → Provider Access.
When to use it
- Create or edit a provider.
- Add or retain an API key.
- Enable or disable provider use.
- Run a health check.
Before you begin
- Sign in to Platform Admin.
- The account must be allowed to view this menu.
Page regions
- 01Name/code, type, and status filters
- 02Provider, authentication, health, and model columns
- 03Create/edit dialog
- 04Status confirmation
- 05Health-check action
Supported operations
Create or edit a provider
- 1
Select Add Provider, or Edit an existing row.
- 2
Enter provider code, name, type, Base URL, and supported authentication method.
- 3
Enter the API key when creating; when editing, leave it blank to keep the stored credential.
- 4
Save and verify the row shows only configured/missing status, never the secret.
The provider configuration is stored; credentials remain masked.
Run a health check
- 1
Find an enabled provider.
- 2
Select Health check on its row.
- 3
Wait for the row-specific check to finish.
- 4
Review success/failure, time, and the business-safe error code/message.
The row records the latest health-check outcome without exposing the API key.
Enable or disable a provider
- 1
Choose the provider status action.
- 2
Enter a status-change reason.
- 3
Confirm the action.
- 4
Review affected models and routes before relying on the new state.
Provider status changes and the reason is recorded.
Business rules and fields
- Stored credentials are never displayed after save.
- Leaving API key blank during edit keeps the current credential.
- OAuth and custom authentication options are labeled unsupported when not implemented.
- Disabling a provider can make dependent models and routes unavailable.
States you may see
What happens next
- Only configured and enabled providers can support normal model tests and routing.
Common problems
The menu or action is missing.
The account does not have the required platform access or the item is not available in the current state.
Ask a platform administrator to verify the account role and the record status.
A save or load action fails.
The session may have expired, validation may have failed, or the service is temporarily unavailable.
Keep the shown request identifier if present, refresh once, correct highlighted fields, and retry. Escalate with the request identifier if it repeats.