On one hand, APIs are fantastic tools that allow us to leverage massive functionality and features with little effort. On the other hand, to make use of these APIs, we have to learn and speak about this functionality in terms of the underlying HTTP implementations instead of the goals we're trying to accomplish. This is fundamentally backwards from good architecture design. This presentation will cover a strategy to make APIs mappable and documentable in machine-readable ways to allow our applications to adapt over time with little human interaction.