Content as a service (CaaS) requirements

Has anyone had experience setting up or working with a technical doc content as a service (CaaS) model? I could be mistaken, but it sounds like you make your content available to anyone (possibly through a REST API) so it can be delivered in any application or context. With CaaS, it seems the writer focuses on the content only, while the app developer worries about the deliverable.

I’m curious what requirements there are to get something like this off the ground, especially if your content is stored in a cCMS. Thanks in advance!