One of the things that striked me when I worked on my first API was that all of service registration, search, payments and certification incur a lot of overhead. Most of these problems are addressed by using third party platforms and middleware (for example Mashape + Kong). But this seems to restrict findability to this one platform and also introduces nontrivial dependencies and fees even for small projects.<p>Therefore, I am trying to find or create systems that do this without this requirement, in a mostly trustless p2p fashion, starting with an extension to the OpenAPI spec:<p><a href="http:&#x2F;&#x2F;i.imgur.com&#x2F;4mmckZ9.png" rel="nofollow">http:&#x2F;&#x2F;i.imgur.com&#x2F;4mmckZ9.png</a>
<a href="https:&#x2F;&#x2F;gist.github.com&#x2F;void4&#x2F;523f23b50e1572e8ef60" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;void4&#x2F;523f23b50e1572e8ef60</a><p>I wonder what comes after that. Most probably different transports and patterns of interactions. <a href="http:&#x2F;&#x2F;iris.karalabe.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;iris.karalabe.com&#x2F;</a> might show how it will look like.