Content
@
https://warpcast.com/~/channel/aichannel
0 reply
0 recast
0 reaction
dylan
@dylsteck.eth
i keep seeing people saying 'agents are the new APIs', but if agents need APIs under the hood to do things then I'm not really sure this is/will be the case this is probably more of a semantic argument, but instead of having my agent call upon another agent, i'd rather have my agent call upon some small kit of highly specialized tools to call curious if anyone has thoughts here! my argument certainly is *not* that services won't interact through LLMs, it's more about how we as developers make our tools accessible to others
6 replies
2 recasts
13 reactions
vrypan |--o--|
@vrypan.eth
API between what? This is the distinction.
1 reply
0 recast
2 reactions
dylan
@dylsteck.eth
yeah exactly — at the end of the day two services need to communicate and pass data(both auth/params as input and the result as output) and there need to be streamlined ways both to categorize what services do and to actually communicate with them so at the end of the day we can call them whatever, all I’m saying is I don’t see why we need to move away from APIs as a standard for interacting with apps(putting aside the whole argument about headless browsing etc)
2 replies
0 recast
1 reaction
dylan
@dylsteck.eth
just now realizing I said “at the end of the day” 2x in a row, lmao
0 reply
0 recast
2 reactions
vrypan |--o--|
@vrypan.eth
Most people (the "marketing" crowd that want to create punchlines) use the term API very loosely. I would say however, that agent will be the interface many programs will use to interact with other services. Much easier to build a string "transfer %d ETH to %x" and post it to an endpoint, than build the actual tx and send it.
0 reply
0 recast
0 reaction
