Responses API - reasoning with store: false i.e. stateless mode

[janaka]

Hi,
Does the SDK expose all the functionality require to use the Responses API in stateless mode?

• how do you set store = false, not on request options.
• how do you set reasoning.encypted_content in the include array. Again not available in request options
• how do you pass back the reasoning item encrypted_content property. CreateReasoningItem() doesn't have an overload for that.
• why aren't IDs on response items exposed? assuming we'll need to send those back also(tbd)?

please just expose the lot, everything on the API spec. if we misuse that's our problem, not yours.

[janaka]

So seems like hardly anybody is using the responses API via the dotnet SDK. The SDK is a bit all over the place is this respect. Naming conventions not matching the OAI API ref and the none existent documentation makes it worse. Sorry, that's just how it is.

So for stateless mode with SDK v2.3.0 when you are mapping between you internal representation and back to OpenAI response items:

• store - is called StoredOutputEnabled in the SDK
• include array - you need to use reflection to set that at the moment. Think i've seen commits with for making this first class. Thanks you for at least making reflect an option here. I'm ok with this as the escape hatch.
• reasoning item encrypted_content - use the OpenAIResponsesModelFactory.ReasoningResponseItem factory. Note: the generic ResponseItem factory on that class doesn't work for assistant messages etc. because they are currently using internal types and the content part collection gets reinitialise if it's not one of the internal types.
• id - my current assumption is that it's not required to have id's for input response items. if streaming you can get at them for all types i think. only custom function calls and corresponding outputs will need the call_id sent back to correlate (i think).