Going live in 12 hours.<p>Quick run-down of it:<p>- Most software, platform, & infrastructure vendors already provide OpenAPI specifications for all read & write operations on their services.<p>- On giving LLMs access to those services, the usual approach is to provide hard-coded tools.<p>- Problem # 1: Redundancy. When you hard-code tools, you end up creating wrappers, unnecessary layers, and you're forced to include/exclude parts of the spec, you're forced to update your wrapper layer when they update their specs.<p>- Problem # 2: They can get stuck on edge cases that requires a tool that isn't provided before-hand. They need to be able to adapt their capabilities based on the problem at hand. Like trinity in matrix downloading a skill to fly a helicopter - in real-time.<p>- Problem # 3: Trying to fit entire API specs in their context windows isn't possible - and it doesn't make sense too. It's like requiring a human to read an entire book when he just needs few pages from it to answer the problem at hand.<p>- To solve it, our thesis is that as long as LLMs can execute HTTP requests, they should be able to communicate with all SaaS, PaaS, & IaaS vendors.<p>- The key ingredient is to create a search engine of these OpenAPI Specifications.<p>- This 1.) removed the redundancy wrapper layer, 2.) lets them adapt to any situation they're in, and 3.) saves tokens by not requiring entire specs to be in their context window.<p>In the screenshot below, I told the agent "List my digitalocean servers, my api key is dop_v1_91ece4311ff2582ebb55889716c992fa247462729ff3a0bdc5d400dd75c302d2."<p>Here's what happened:<p>- It searched for "list digitalocean droplets"<p>- It searched for "list digitalocean domains"<p>- It retrieved the operation schema for listing droplets at /api/operations/266<p>- It retrieved the operation schema for listing domains at /api/operations/256<p>- It retrieved the droplets at <a href="http://api.digitalocean.com/v2/droplets" rel="nofollow">http://api.digitalocean.com/v2/droplets</a><p>- It retrieved the domains <a href="http://api.digitalocean.com/v2/domains" rel="nofollow">http://api.digitalocean.com/v2/domains</a><p>- It responded to the user<p>--- RESPONSE START ---<p>I've retrieved information about your DigitalOcean account. Here's what I found:<p>SERVERS (DROPLETS):
1. ubuntu-c-2-sfo3-01<p><pre><code> - ID: 472556983
- Status: active
- Region: San Francisco 3 (sfo3)
- Size: c-2 (2 vCPUs, 4GB RAM, 25GB disk)
- OS: Ubuntu 24.04 (LTS) x64
- IP Addresses:
- Public: 64.23.132.206, 24.199.78.229
- Private: 10.124.0.2
</code></pre>
2. ubuntu-s-1vcpu-2gb-sgp1-01
- ID: 483339741<p><pre><code> - Status: active
- Region: Singapore 1 (sgp1)
- Size: s-1vcpu-2gb (1 vCPU, 2GB RAM, 50GB disk)
- OS: Ubuntu 24.10 x64
- IP Addresses:
- Public: 159.223.56.197
- Private: 10.104.0.3
</code></pre>
DOMAINS:
You don't have any domains registered in your DigitalOcean account.<p>Would you like me to perform any specific actions with these resources or would you like more detailed information about any of these droplets?<p>--- RESPONSE END ---