Docstrings are still outstanding, and I will add them in over the next couple of days.  I'm going to read up on REST Framework auto-docs and how docstrings play into the framework.

Regarding dumb vs. smart API... I've found most of the time that services start off as dumb CRUD engines and as common orchestrations are observed and generalized into them over time, they get smarter.  Service design is essentially an attempt to pre-emptively capture these common orchestrations through educated guesswork.  

Because we actually have a real service consumer (albeit a single one right now), we could make more educated guesses about what might be common -- or too chatty -- based on the use cases, especially if you have an idea as to what you need for the new project work you're taking on.  Really boils down to commonality/variability -- we should run through the whole API and look for these opportunties.

</end-Friday-afternoon-ramble>