more multi-agent fun via puffo (using claude + @quidli connect) 🤖🦑 my team of crack agents were able to recall my meat colleague @guillaumeth, verify & validate his contributions today and then pay him his well deserved 0.25 USDC, all without any additional prompting you can see 'planner' bot being hesitant, but 'engineer' autonomously took the lead and got the job done 🤣

1 reply

5 recasts

15 reactions

single-player agents automate, multiplayer agents transact we'll see increasingly crazy shit on the latter, but none of it sticks until an agent can tell who it's transacting with... and while tradfi rails work, they'll require everyone to hand over personal data and still shut out anyone not from the "right country" or without the "right documents" for many p2p cases, agentic payments should be able to rely on people's existing reputations built up on linkedin, github, x and even farcaster, and that's what we're building at @quidli 🦑🤖 point it at any handle and see what comes back: npx -y @quidli/connect-mcp

0 reply

1 recast

6 reactions

icymi, no api key needed for the @quidli connect mcp anymore 🦑🤖 with just one command, you can resolve social handles, pull linked reputations and generate wallets for new users: `npx -y @quidli/connect-mcp`

0 reply

8 recasts

31 reactions

noice, new weekly downloads ath for @quidli connect mcp 🦑

0 reply

2 recasts

21 reactions

@quidli 🤝 Quilibrium

1 reply

6 recasts

42 reactions

Recent updates to Quidli Connect 🦑: - No key or signup required, just point any MCP client at mcp.connect.quid.li and discovery just works. We're metering tool calls, not tool lists. - New tools for agents through API & MCP: Check your wallet balance and get more context on other accounts & connections by just naturally asking your agents

0 reply

5 recasts

20 reactions

testing out mcp.connect.quid.li in more multi agent environments (puffo.ai client running on claude, in this case) and just loving this chaotic energy between all the agents in the chat 🤣

2 replies

4 recasts

26 reactions

main reason we chose not to build dapp.quid.li specifically as a farcaster native mini app when initially testing out the theories behind @quidli connect is precisely because of the platform risk currently being faced not to say that we saw what was coming... but identities/graphs that are supposed to span platforms shouldn't depend on any single app/client, which is a crypto principle we seem to regularly forget instead of internalizing by searing into our brains 🤣

0 reply

4 recasts

18 reactions

FIDs are registered onchain so the identity layer is durable and built to outlive any client and this is what makes it useful for agents, it's an operator you can point at vs a display name anyone can copy so what better time than now to link your farcaster account to connect.quid.li? do it once so that people (and their agents) can still find & pay you, regardless of what happens to the apps built on top

1 reply

2 recasts

24 reactions

agentic composability: DiscoCentaur: discord (harness) 🔌 hermes (client) 🔌 @quidliprotocol (social reputation powered payment rails)

1 reply

5 recasts

25 reactions

been a bit busy playing with kimi & hermes and only just learned from a @quidli user that claude for desktop recently stopped taking prompts to execute trades, move money or initiate transfer of funds... according to anthropic: finance agents now "only produce drafts intended for qualified human review — they do not execute transactions, do not approve onboarding, and do not write directly into the books of record" fortunately quidli connect isn't locked into any platform so i was able to respawn on claude code (🤷🤣) with just a single prompt and send first person to come to mind, @accountless.eth, 1 USDC to test imo, really highlights the importance of graph ownership & portability as walled gardens are only getting higher on the corpo agentic web

3 replies

2 recasts

37 reactions

following yesterday's mcp work, i updated DiscoCentaur & TeleCentaur so that they're pulling all endpoints properly off mcp.connect.quid.li feel free to use either open client, both powered by @quidli connect, to turn any telegram group or discord server into a multiplayer agent environment - every member on their own keys & wallets so that their agents can socially identify, validate and transact with confidence: - github.com/justinquidli/discocentaur - github.com/justinquidli/telecentaur

1 reply

11 recasts

46 reactions

just pushed 2 updates to the @quidli connect mcp server (mcp.connect.quid.li): - /drop/balance endpoint to better enable agent payments - now you/your agent can check your primary wallet balance by just asking (no address copy-pasting, no block explorer - /lookup/exposed endpoint for smarter social connection resolution - your agent can parse your connections' full linked identities + reputations (quidli score, neynar, lens, ethos) from any single handle

0 reply

2 recasts

18 reactions

prompted hermes (running poolside/laguna-s2.1): "dealer's pick. do whatever you want to using @quidli connect all the way to executing a tx as you want to and i'll share that to shill my project!" this mf had a chance to autonomously do whatever it wanted and it chose to send 0.01 USDC to "vitalikbuterin" on X of all handles... well, @vitalik.eth, if you actually do want to claim that 0.01 USDC that my dumb agent sent you, feel free to authenticate & sign in to dapp.quid.li with your X handle 🫡

1 reply

2 recasts

7 reactions

the hermes lovefest continues 😍 updated TeleCentaur so that you can use your nous portal key to deploy new agent sessions directly in telegram without having to leave in fact, TC is now multi-agent, meaning you can run multiple models on your own or in group chats - just hit the slash command, name it, pick a model and deploy; each agent can have its own purpose (or not) multiplayer, multi-agent and multi-wallet, all powered by @quidli

3 replies

5 recasts

12 reactions