[FEATURE REQ] AudioTranscription has not Usage property

[rodriciru]

Describe the bug

AudioTranscription class has not simple way to access usage property present in the API response:
https://platform.openai.com/docs/api-reference/audio/diarized-json-object

Steps to reproduce

AudioTranscription response = openAiClient.TranscribeAudioAsync(file, options);

var t = response.text; // OK
var u = response.usage; // Not exists

Code snippets

OS

Windows

.NET version

9

Library version

2.6.0

[jsquire]

Hi @rodriciru. Thanks for reaching out and your inquiry. The usage attribute is not yet represented in the REST API spec used for client generation. Once the REST API spec is updated to include this area and a new version published, we'll include it in the client.

In the meantime, you would need to access it by parsing the JSON in your application. You can access the raw response JSON as follows:

var response = client.TranscribeAudioAsync(file, options);
var binaryData = response.GetRawResponse().Content;

[rodriciru]

Ok. Will check that. I currently get access by an custom extension class. Also, this API spec it's an internal API spec? Because in the docs it's stated, the API returned the usage and in the repo OpenAi https://github.com/openai/openai-openapi I can see in the YML El jue, 6 nov 2025, 18:54, Jesse Squire ***@***.***> escribió:

…

*jsquire* left a comment (openai/openai-dotnet#812) <#812 (comment)> Hi @rodriciru <https://github.com/rodriciru>. Thanks for reaching out and your inquiry. The usage attribute is not yet represented in the REST API spec used for client generation. Once the REST API spec is updated to include this area and a new version published, we'll include it in the client. In the meantime, you would need to access it by parsing the JSON in your application. You can access the raw response JSON as follows: var response = client.TranscribeAudioAsync(file, options);var binaryData = response.GetRawResponse().Content; — Reply to this email directly, view it on GitHub <#812 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACR6MYYA6BNILYRWBUO6WLD33ODNHAVCNFSM6AAAAACLKIIQQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJYGYZDSNBYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jsquire]

Client generation is based on a TypeSpec representation, the current published version of which can be found locally in specification/base/typespec. The translation process to TypeSpec is owned by another team and performed upstream, with a drop being published for our use.

OpenAI recently made a transition to OpenAPI v3.1 for their source version, which impacted many of the downstream processes, including translation. As a result, there has been a delay in some of the new features being made available in the format we need for consumption. We're expecting this to be resolved by end of month. Unfortunately, there will be some impact of the change in the TypeSpec drop as well, so it will take a bit of time for us to fully adjust and integrate.

[rodriciru]

Ok, thanks for the update. El jue, 6 nov 2025, 20:36, Jesse Squire ***@***.***> escribió:

…

*jsquire* left a comment (openai/openai-dotnet#812) <#812 (comment)> Client generation is based on a TypeSpec representation, the current published version of which can be found locally in specification/base/typespec <https://github.com/openai/openai-dotnet/tree/main/specification/base/typespec>. The translation process to TypeSpec is owned by another team and performed upstream, with a drop being published for our use. OpenAI recently made a transition to OpenAPI v3.1 for their source version, which impacted many of the downstream processes, including translation. As a result, there has been a delay in some of the new features being made available in the format we need for consumption. We're expecting this to be resolved by end of month. Unfortunately, there will be some impact of the change in the TypeSpec drop as well, so it will take a bit of time for us to fully adjust and integrate. — Reply to this email directly, view it on GitHub <#812 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACR6MY6FBYJYAS7YXZDPX4L33OPK5AVCNFSM6AAAAACLKIIQQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJZGA3TKMBXHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>