We have covered Machine Learning APIs before, including BigML.com, Algorithms.io and others. We now continuing the series in an interview with Simon Chan of Prediction.io which aims to further bring machine learning closer to the common man, in an easier interface. PredictionIO is an open source machine learning server for software developers to create predictive features, such as personalization, recommendation and content discovery.
Swift IQ belives Machine Learning as a Service (MLaaS) will become a key market in the near future as more providers look to integrate predictive APIs with their customer transaction data. After presenting at the recent API Strategy and Practice Conference, Swift IQ CEO Jason Lobel spoke with ProgrammableWeb about how businesses can use an API-driven approach to improve their “adaptive intelligence”, and shares four techniques that can be tested immediately.
Here is an interview with Scott Gimpel Founder and CEO of FantasyData.com. The site used to be known as NFLdata.com and provides NFL statistics. The site claims to have almost 25 million API calls /month during football season with over 300 developers working with it’s API.
A new API description language is looking to help out where many modern APIs get stuck: at the design phase. Officially announced, today, the RESTful API Modeling Langauge (aka RAML) offers a format friendly to both humans and machines. It also centers on re-use of results within responses. Like other description languages, it also offers the potential for post-design benefits such as streamlining documentation, enabling interactive consoles and generating client libraries. Though not formally announced at the time, the format was originally revealed earlier this month.
Open APIs are upending the ecommerce business model and forcing developers to seek out more realtime tools to ensure a positive customer experience. Speaking with ProgrammableWeb at the recent API World conference in San Francisco, Tony*, a lead developer with an online retailer, discussed some of the unique impacts that face retail when using APIs to enhance content delivery.
Here is an interview with Brandon Levy, Co Founder and CEO of Stitch Labs. The company recently raised $3.5 million in Series A financing and recently announced its latest integration partner, Vend, the top iPad point-of-sale (POS) software for retailers.
“Back in 2005, getting API design unstuck from the WS-* rut was a matter of convincing developers to stop hitting themselves in the head with a hammer. The benefits were obvious. Now it’s more like convincing developers to adopt a healthy diet to avoid a heart attack down the road.” With the release of his new book, Leonard Richardson surveys the state of API design and offers glimpses at how to move it forward.
When it comes to sharing personal data, Robert Scoble lets it all hang out. He is not afraid to tell people anything about himself, because he believes that the information mobile devices and sensors and apps collect on him can improve his life.
We have all been there many times, trying to resolve complicated and important issues in an automated world only to be met with a frustrating series of dead ends. This is funny coming from the Director of Sales for a popular Web Service that does just that, solves important brand protection problems for our clients utilizing our profanity filter and image and video moderation services. But, with these new leaps and bounds in technology, we still require the old fashioned human touch.
It’s an inevitability of creating APIs is that at some point you’ll need to make a breaking change. No matter how much you attempt to consider the future, unforeseen forces can disable your best intentions. If you have a versioning plan, you’ll be one step ahead as you push out a new version of your API. There are many thoughts on API versioning, but this post will focus on data from the ProgrammableWeb directory, specifically with the two most common methods: the endpoint sub-domain or directory.