-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Name and Version
latest
What is the problem this feature will solve?
Problem
AsyncDial (and its sync twin Dial) currently expose resource accessors for files, bucket, metadata, chat completions, deployments (list only), and applications. Several DIAL Core API endpoints have no equivalent in the library, which forces downstream projects to maintain a separate raw HTTP client alongside AsyncDial. The missing operations are:
- GET /openai/deployments/{name} — single-deployment lookup
- GET /v1/deployments/{name}/configuration — deployment runtime configuration (JSON Schema)
- GET /openai/toolsets/{name} — toolset metadata
- GET /openai/models/{name} — model info including pricing and limits
- POST /v1/ops/resource/per-request-permissions/grant — share resources between deployments
Proposed Solution
Extend the existing Deployments/AsyncDeployments resource with two new methods, and introduce three new lightweight resource classes following the established Resource / AsyncResource pattern.
What is the feature you are proposing to solve the problem?
Proposed Solution
Extend the existing Deployments/AsyncDeployments resource with two new methods, and introduce three new lightweight resource classes following the established Resource / AsyncResource pattern.
What alternatives have you considered?
No response