To migrate Chromium Status into Sheriff-o-Matic, we'll need to get a direct mapping of the tree APIs into Sheriff-o-Matic. As much as possible, we should try to make Sheriff-o-Matic's implementation a direct mapping of the same endpoints, so that Sheriff-o-Matic tree statuses can be replaced. 
These APIS include: 

* /api/v1/tree/:treename/current - By default, outputs an HTML Element displaying the tree status that’s loaded into other apps (I know :/). Has text and json formats as well. Ie: https://chromium-status.appspot.com/current -> https://sheriff-o-matic.appspot.com/api/v1/tree/chromium/current

* /api/v1/tree/:treename/allstatus - List of all statuses. Can be retrieved in json format as well. Ie: https://chromium-status.appspot.com/allstatus -> https://sheriff-o-matic.appspot.com/api/v1/tree/chromium/allstatus

* /api/v1/tree/:treename/status - Returns a boolean for whether the tree is open or not Ie: https://chromium-status.appspot.com/status -> https://sheriff-o-matic.appspot.com/api/v1/tree/chromium/status


The non-tree APIs such as breakpad, profiling, and LKGR can either be deprecated or should be handled separately. The non-tree APIs are generally unused by the vast majority of status apps anyways.