[davmar]

i think this type of interaction is the future in lots of areas. i can imagine we replace API's completely with a single endpoint where you hit it up with a description of what you want back. like, hit up 'news.ycombinator.com/api' with "give me all the highest rated submissions over the past week about LLMs". a server side LLM translates that to SQL, executes the query, returns the results.

this approach is broadly applicable to lots of domains just like FFMpeg. very very cool to see things moving in this direction.

[sitkack]

Do you envision the LLMs creating a protocol? Would the caller supply the schema for the response?

[andai]

I mentioned here recently that I let LLMs design the APIs which they are going to use. I got quite a negative response to that, which surprised me.

[halJordan]

The big protocol doing this is called "Model Context Protocol" and it should've been a widely read/discussed post except hn has taken a wide anti-ai stance

[varispeed]

Imagine that every API will be behind government gateway, checking all the queries before passing on to the real API and then checking its replies.

[mochajocha]

Except you don't need an LLM to do any of this, and it's already computationally cheaper. If you don't know the results you want, you should figure that out first, instead of asking a Markov chain to do it.

[tomrod]

I believe this approach is destined for a lot of disappointment. LLMs enable a LOT of entry- and mid-level performance, quickly. Rightfully, you and I worry about the edge cases and bugs. But people will trend towards things that enable them to do things faster.