README.md in sidekiq-expected_failures-0.2.0 vs README.md in sidekiq-expected_failures-0.2.1

@@ -1,10 +1,12 @@
 # Sidekiq::ExpectedFailures
 
 [![Code Climate](https://codeclimate.com/github/emq/sidekiq-expected_failures.png)](https://codeclimate.com/github/emq/sidekiq-expected_failures)
 [![Build Status](https://travis-ci.org/emq/sidekiq-expected_failures.png?branch=master)](https://travis-ci.org/emq/sidekiq-expected_failures)
 [![Coverage Status](https://coveralls.io/repos/emq/sidekiq-expected_failures/badge.png)](https://coveralls.io/r/emq/sidekiq-expected_failures)
+[![Dependency Status](https://gemnasium.com/emq/sidekiq-expected_failures.png)](https://gemnasium.com/emq/sidekiq-expected_failures)
+[![Gem Version](https://badge.fury.io/rb/sidekiq-expected_failures.png)](http://badge.fury.io/rb/sidekiq-expected_failures)
 
 If you don't rely on standard sidekiq's retry behavior and you want to track exceptions, that will happen one way, or another - this thing is for you.
 
 ## Installation
 
@@ -52,10 +54,10 @@
 
 This is how web interface looks like:
 
 ![](http://i.imgur.com/7Fe8voD.jpg)
 
-It logs each failed jobs to to redis list (per day) and keep global counters (per exception class as a single redis hash).
+It logs each failed jobs to to redis list (per day) and keep global counters (per exception class as a single redis hash). If you would like to get that counter as JSON response (for some external API usage for example) you can use path `expected_failures/stats`.
 
 ### Default expected failures
 
 You can configure defaults for all your workers (overridden completely by specifying `expected_failures` hash inside `sidekiq_options` - per worker).