A .NET Standard library for accessing IBM Watson cognitive services like Assistant, Discovery, and Speech-to-Text.
Watson Developer Cloud .NET Standard SDK is a client library that enables .NET developers to integrate IBM Watson's AI services into their applications. It provides a unified interface to access cognitive services like speech recognition, language translation, and natural language understanding, simplifying the process of adding AI capabilities to .NET projects.
.NET developers building applications that require AI-powered features such as chatbots, document analysis, speech processing, or language translation using IBM Watson services.
Developers choose this SDK for its official support, comprehensive coverage of Watson services, and seamless integration with the .NET ecosystem, offering a production-ready solution for cognitive computing in C# and .NET applications.
:new::new::new:.NET Standard library to access Watson Services.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates multiple Watson AI services, such as Assistant, Discovery, and Speech to Text, into a single .NET library, simplifying access as noted in the README's installation section.
Supports IAM tokens, username/password, and CloudPak for Data, with examples in the README for each method, including credential file management for easier setup.
Exposes response headers, status codes, and raw JSON, as detailed in the README, allowing developers to troubleshoot and integrate more effectively.
Includes proxy support and SSL verification disablement, as shown in the README examples, making it suitable for behind-firewall or testing environments.
The README explicitly states the SDK is deprecated, with no new NuGet updates and only community PRs for maintenance, risking obsolescence and security issues.
Version 6.0.0 dropped services like Tone Analyzer and Natural Language Classifier, forcing migration to alternatives like Natural Language Understanding without SDK updates.
Users must manually handle endpoint URL changes and service deprecations, as warned in the README, adding overhead compared to actively maintained SDKs.