Hi Terence,

I enjoyed your list, but have a followup question. Coming from the world of startups, I know a ton of companies that have fascinating data available to play with, that they would be open to getting out in the world, but never expose it via an API because they don’t have the resources to “do it right”. I’d far prefer get a minimal (though still usable) set of things to play with than nothing at all… Do you have an opinion on which pieces of these are necessary for an MVP API? For example, I’d personally bias towards simplicity and clear documentation of parameters and responses, while not caring as much about variety of supported response types or libraries. Thoughts?