anchor.diff:                      }
                   }
               }
  -        }]+        }]
  +        
  +## Status [/v1/status]
  +The status endpoints gives details about the node currenctly connected to. It also allows the node to be 
  +activated and deactivated.
  +
  +### get status [GET]
  +Get the status of the current node and the low level daemons running on it.
  +
  ++ Response 200 (application/json)
  +
  +        {
  +        }
  +        
  +### activate the node [POST]
  +Activate the node currently connected to. This will start the underlaying daemons used to communicate with 
  +the cluster.
  +
  ++ Response 200 (application/json)
  +
  +        {}
  +        
  +### deactivate the node [DELETE]
  +Deactivate the node currently connected to. This will stop the underlaying daemons used to communicate with 
  +the cluster. As a result, after calling this endpoint, the node will not be an active member of the cluster.
  +The node will not be removed from the cluster though, so it can be reactivated later.
  +
  ++ Response 200 (application/json)
  +
  +        {}
positive.code:             }
          }
          
  ## Events [/v1/events]
  Events are the result of actions happening on the cluster. They are meant to get insights in what is happening
  on the cluster
          
  ### list all events [GET]
  
  + Response 200 (application/json)
  
          []
          
  ## Nodes [/v1/nodes]
  Nodes are the dna of the cluster. These endpoints give you some insights into what they are doing, but also
  
negative.code: 
  ### install an app [POST]
  
  Install a new app onto the cluster.
  
  + Request (application/json)
  
  