It wouldn&#x27;t be hard to build in tools to aid discoverability. A &#x27;help&#x27; function that returns a list of features for example. That&#x27;s pretty much what WSDL[1] tries to be, but that&#x27;s really to hard to use well. If there were a much more flexible &quot;natural language&quot; interface to it then it&#x27;d make finding and consuming APIs both easier and more robust.<p>I&#x27;m just musing on the possibility really. I&#x27;m absolutely sure there&#x27;d be difficulties in the technical implementation, and obviously it&#x27;d be quite inefficient compared to a known and well-defined API, but if it could be made to work the advantages may outweigh those problems. Plus, implementing it for humans goes 90% of the way to implementing it for computers too, so it&#x27;s almost zero-cost if you&#x27;re considering a chat interface to your service. It&#x27;s something to think about anyway.<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Web_Services_Description_Language" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Web_Services_Description_Langu...</a>