Last Thursday, telecom giant AT&T announced they would be opening several of their "Watson" speech recognition APIs to outside developers in June. While it may be a while before any killer apps hit the scene, a major player like AT&T getting into the speech-to-text API game should not be ignored.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?