Cool! I'll play with it. I'm with you on agents communicating over nostr. openagents.com and fewsats.com are the best examples of this vision I've seen so far. cc @npub1tlv6...7fdm I guess DVMs as well, though I've yet to find a user friendly way to interact with these - what's the best DVM client right now? cc @Dustin Dannenhauer @PABLOF7z

Replies (2)

Im an open agents subscriber. Didnt know about fewsats, looks cool, but requires email to login AFAICT. I also am looking for something more user friendly than DVMs. I have may own agent framework in any case called #sandymount and I've tried to add DVMs many times, but yet to get that over the line. I think it will be easier to do next year. I think with nostr is that you simply need a business to add nostr. Hopefully with a professional relay. No one seems to have done that yet. Which is odd, after all this time.
DVMs are more infrastructure imo, I don’t see them as something users will interact with directly (at least for most DVMs). The most used DVM right now is feed sorting algorithms, and clients make this user friendly and call the DVMs in the background (the user may not even know it’s DVMs that are doing the work). We haven’t really had multi DVM use cases yet (although folks are working on them). I think of DVMs as modules that could comprise agents, and the space is still so early. For example, we need libraries where you can call a DVM just like you would call an API (a python library for this is on my to do list). Many people building agents are using lots of APIs right? DVMs would replace these API calls and offer some neat tradeoffs.