Repo Documentation of the Data-api needs to include a human-readable, up-to-date spec of endpoints and methods

This might be a task for a new developer intent on learning Mulesoft and getting up to speed with the project(s).
The documentation generated in Anypoint is useful and we need some of it to live in the github repo(s).
Manual updates and screencaps are acceptable but labor-intensive and prone to human error and falling out of date.
Better would be a dynamic solution, such as swagger.io, that helps inform everyone who comes to the repo what is going on there, and also is a linkable resource for the client projects and issues/tickets.