[mattbrewsbytes]

A REST API typically does the mundane CRUD operations on data so you would definitely need a database.

More importantly, who is the customer? Companies w/o developers wouldn't probably be building an API, they would be looking at full services they can just pay for with a CC. Companies with developers can scaffold a REST API with some web development frameworks out of the box.

Who is the customer and what value does this SaaS bring?

How will you handle API authentication, rate-limits, scaling, analytics, etc.?

[dkneeland]

This is something I was thinking about. I think I would marketing it at people who need fast time-to-market solutions or prototypes so they don't have to go through the original hassle of setting up a server and scaffolding the infrastructure before even getting to start development of the interface. Thanks for the comment by the way!

edit: I think maybe marketing it as a non permanent solution could work. As well as giving customers the flexibility to make it a permanent solution if they are happy with it.