Name and Version
latest
What is the problem this feature will solve?
Please add support for the DIAL /v1/user/info endpoint.
What is the feature you are proposing to solve the problem?
Motivation
StatGPT Backend needs to retrieve authenticated user information from DIAL. This is currently implemented with a local direct HTTP call:
To fully replace local DIAL wrappers with aidial-client, this endpoint should be available through the SDK.
Proposed API
For example:
user_info = await async_client.user.info()
or:
user_info = await async_client.users.me()
Expected Behavior
- Use the same authentication configuration as the rest of the client.
- Return a typed model if the response schema is stable, or
dict[str, Any] if not.
- Raise existing
DialException-style errors on HTTP failures.
Use Case
StatGPT Backend uses DIAL authentication context to resolve the current user. Without SDK support, this still requires custom HTTP code even after migrating file and model operations to aidial-client.
What alternatives have you considered?
No response
Name and Version
latest
What is the problem this feature will solve?
Please add support for the DIAL
/v1/user/infoendpoint.What is the feature you are proposing to solve the problem?
Motivation
StatGPT Backend needs to retrieve authenticated user information from DIAL. This is currently implemented with a local direct HTTP call:
To fully replace local DIAL wrappers with
aidial-client, this endpoint should be available through the SDK.Proposed API
For example:
or:
Expected Behavior
dict[str, Any]if not.DialException-style errors on HTTP failures.Use Case
StatGPT Backend uses DIAL authentication context to resolve the current user. Without SDK support, this still requires custom HTTP code even after migrating file and model operations to
aidial-client.What alternatives have you considered?
No response