Dashboard
The dashboard summarizes runtime readiness. It does not modify configuration; it helps determine whether the complete path from provider key to downstream request is ready.
Workspace states
| State | Meaning | Recommended action |
|---|---|---|
| Incomplete | A model resource or API configuration is missing | Follow the shortest setup path shown on the page |
| Callable | Platform model or connected model resources and an API configuration are ready | Send a request with an access key |
| Needs attention | The basic path exists, but recent requests or upstream health are abnormal | Check the client error and test the upstream |
Main sections
Upstream access
Shows the number and health of enabled upstreams. A warning means at least one enabled upstream failed its latest health check.
Model resources
Shows discovered routable models and their detection status. If an upstream exists but this section is empty, run discovery from Model resources.
API configurations
Shows how many configurations are ready to receive requests.
Recommended check order
- Verify that at least one platform model or connected model resource is routable.
- When using a connected model, verify its upstream is healthy.
- Verify that the API configuration is enabled and has candidates.
- Send a minimal request.
Common states
For Incomplete, inspect model resources and the API configuration. Quickstart may continue without a connected upstream or discovered model, but a configuration with no candidates cannot serve calls. For Needs attention, record the client error and test the selected resource or upstream.