<story><title>AI teaches itself to use an API</title><url>https://twitter.com/DYtweetshere/status/1631349179934203904</url></story><parent_chain></parent_chain><comment><author>paxys</author><text>So the AI can learn to use APIs that follow perfect RESTful semantics, are fully documented and intuitively behave exactly like one would expect.&lt;p&gt;Our jobs are safe.</text></comment>
<story><title>AI teaches itself to use an API</title><url>https://twitter.com/DYtweetshere/status/1631349179934203904</url></story><parent_chain></parent_chain><comment><author>mistrial9</author><text>in the Toolformer paper, it seems what they are doing is :&lt;p&gt;* take a performant language model (copied from some other team e.g. GPT-J)&lt;p&gt;* show the machinery that it can learn new tokens using one or more tools from a provided set of tools ... e.g. WikiSearch tool&lt;p&gt;* demonstrate that the sequence of characters in the full API call content, has some effect.. e.g. no reply, useless content, or content that helps predict another token. Save that complete set of characters in the API call as an entry&lt;p&gt;* run a learning session with tool calls to APIs, improve the model for resolving known or new tokens (queries with answers)&lt;p&gt;* show the model that it can try new combinations itself (!)&lt;p&gt;* let the machinery try API calls itself to resolve tokens&lt;p&gt;* minimize loss functions for API results&lt;p&gt;comments - this is strikingly different than some RDF hard-wired data store.. it is using huge numbers of failed attempts to find results that work. The results that work are complete API calls as type string. It does not seem to care about &amp;quot;learning&amp;quot; the contents of the API calls, just that it is methodical about remembering API calls that work, and retrying those&lt;p&gt;not a specialist, feedback welcome</text></comment>