Of the many APIs we published this week, five were highlighted on the blog by our team of writers. In this post, we’ll shine a spotlight on those five, which included the Merriam-Webster Dictionary API for definitions, synonyms and antonyms. We said Webster’s API would be good news to education apps that want to include words–and their definitions–in either strictly educational or word play format. Read more in the Webster API post or check out the Merriam-Webster API profile.
The Microsoft Translator API isn’t new, but it’s getting a major rework as it moves to the Azure Marketplace. The technology is allows developers to integrate an automatic language translation system into their workflows. We wrote that there are now translations for specific industries because language is used differently in, say, agriculture and technology. Read more in the Microsoft Translator Hub post or check out the Microsoft Translator API profile.
The Zaarly API enables any website to provide users with a button to express a desire to have something done locally. That sounds vague, but that’s part of the promise. We wrote that everything from simple errands to complex products can be requested via Zaarly. Read more in our Zaarly API post or check out the Zaarly API profile.
Rote, but still extremely human, tasks are a growing area of APIs. The TextMaster API may become a clearinghouse for those associated with copywriting, proofreading and even translation. We called TextMaster a “second pair of eyes” for reviewing content. Read more in our TextMaster API post or check out the TextMaster API profile.
Don’t think this human-powered-via-API thing is a trend? We also highlighted the Humanoid API this week, which puts the company’s 30,000+ workforce at the end of your API calls. We wrote that popular areas are data entry, data accuracy and, interestingly, sentiment analysis. Read more in our Humanoid API post or check out the Humanoid API profile.