APImetrics Launches Single Number Score for API Health

APImetrics, an API performance solution provider, has developed a single number score that reflects the health of an API. This Cloud API Service Consistency (CASC) score is designed for both consumers and providers of data to quickly assess the effectiveness of the API passing the data between parties. The CASC score reports an API's uptime, deviations from perfect uptime and ideal speed, the standard deviation of latency, and more.
In an interview with GeekWire, APImetrics CEO and co-founder, David O'Neill, described the CASC score as "a credit score, a single trackable number that reflects how much time you'll waste looking into problems reported by clients and users." A score of 800-999 indicates good basic performance (i.e. roughly a few issues per month). A score of 600-800 indicates average performance (i.e. roughly a dozen issues per month). A CASC score below 600 indicates that an API experiences multiple problems on a weekly basis. Additionally, an arrow next to the score displays whether the score has improved or worsened since the API was last checked.   
APImetrics believes a single score allows users across an organization to quickly assess API health. "We're trying to take out the noise and allow a focus on the signal," O'Neil continued. As the API economy continues to grow, companies are increasingly dependent on API health to access the data and services of third parties. Accordingly, API service levels are critical to effective exchange of data and services. APImetrics hopes to provide actionable feedback on such service levels. 
APImetrics is not alone in its pursuit of an easy to understand API health score. Wicket Labs recently launched a similar service with the goal to address the cloud's "blind spot". Both companies squarely understand that regardless of how valuable the data or service on the other side of the wall is, a healthy API is critical to the effective exchange between two parties. Visit the APImetrics website to learn more. 

Be sure to read the next Testing article: Why These Four API Errors Are Subtle but Expensive


Comments (0)