Timeline for Official Responses API Support in .NET SDK #680
                  
                    
                      buddhikaprasad
                    
                  
                
                  started this conversation in
                General
              
            Replies: 1 comment
-
| 
         This is exactly right. I actually switched from the official OpenAI NuGet package to making direct HTTP calls because of the missing Responses API support with the latest stuffs Having to do raw JSON requests isn't ideal, but at least it works reliably with all the new features.  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
I see that the latest .NET SDK includes Responses API support, but it’s currently marked as experimental.
Since the Responses endpoint is now the recommended way forward (replacing older Assistants/Chat APIs), I’d like to know:
What’s the timeline/ETA for promoting Responses from experimental to stable in the .NET SDK?
Are there any breaking changes expected between the experimental implementation and the stable one?
Should we start building production features on top of the current experimental Responses API, or wait until it’s officially stable?
Beta Was this translation helpful? Give feedback.
All reactions